# CVE-2026-85574: Unbounce Landing Pages 1.1.1 - 1.1.4 - Subscriber+ Reverse-Proxy Target Hijack via set_unbounce_domains

> Authenticated users can hijack the reverse-proxy target to serve arbitrary content from the site's origin due to missing authorization checks.

- **Severity:** High 8.0 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 19 Sep 2026
- **Updated:** 19 Sep 2026
- **Also known as:** GHSA-jqrj-3hxj-9rmf

## What is CVE-2026-85574?

CVE-2026-85574 is a high-severity missing authorization vulnerability in Unknown Unbounce Landing Pages, published on 19 Sep 2026. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link.

### Official 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.

Weakness: CWE-862 (Missing Authorization)

## Which versions are affected by CVE-2026-85574?


## How do I fix CVE-2026-85574?

No fix has been published for CVE-2026-85574 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-85574 being exploited?

There is no known exploitation of CVE-2026-85574 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-85574 and fix it if it is affected.

What it is: CVE-2026-85574 is a high-severity missing authorization vulnerability in Unknown Unbounce Landing Pages, published on 19 Sep 2026. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2026-85574 in the wild and no public exploit code.

Affected product: Unknown Unbounce Landing Pages. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-85574/ (Markdown: https://insights.sbomify.com/CVE-2026-85574/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-85574
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-85574
- OSV: https://osv.dev/vulnerability/CVE-2026-85574

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-85574/
Summaries are generated and may contain mistakes; the official description above is the record.