# CVE-2026-121759: Fusion Page Builder < 1.7.1 - Contributor+ Arbitrary Post Trashing via IDOR


- **Severity:** Medium 4.9 (`CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:N/I:H/A:N`)
- **Exploited in the wild:** Not known
- **Fix available:** No
- **Published:** 9 Nov 2026
- **Updated:** 9 Nov 2026
- **Also known as:** GHSA-vmmh-jvfw-c7h2

## What is CVE-2026-121759?

CVE-2026-121759 is a medium-severity vulnerability in Unknown Fusion Page Builder, published on 9 Nov 2026. 

### Official description

The Fusion Page Builder WordPress plugin before 1.7.1 does not check that the user owns the content it moves to the trash, which could allow users with a role as low as Contributor to trash arbitrary posts and pages, or delete them permanently where the trash is disabled.

Weakness: CWE-639 (Authorization Bypass Through User-Controlled Key)

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


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

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

## Is CVE-2026-121759 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-121759 is a medium-severity vulnerability in Unknown Fusion Page Builder, published on 9 Nov 2026. 
Exploitation: There is no known exploitation of CVE-2026-121759 in the wild and no public exploit code.

Affected product: Unknown Fusion Page Builder. 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-121759/ (Markdown: https://insights.sbomify.com/CVE-2026-121759/index.md)
```

## Sources

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

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