# CVE-2026-53739: Yoast Duplicate Post through 4.6 Cross-Site Request Forgery via duplicate_post_dismiss_notice

> Attackers can trick authenticated users into suppressing admin notices network-wide via a CSRF vulnerability in the Yoast Duplicate Post plugin.

- **Severity:** Medium 5.1 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:A/VC:N/VI:L/VA:N/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 10 Jun 2026
- **Updated:** 11 Jun 2026
- **Also known as:** GHSA-8jhr-hxr5-g2rc

## What is CVE-2026-53739?

CVE-2026-53739 is a medium-severity vulnerability in Yoast Duplicate Post, published on 10 Jun 2026. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.

### Official description

Yoast Duplicate Post through 4.6 contains a cross-site request forgery vulnerability in the duplicate_post_dismiss_notice handler, which verifies no nonce or capability. Attackers can trick any authenticated user into sending a request that sets the duplicate_post_show_notice site option, suppressing admin notices network-wide.

Weakness: CWE-352 (Cross-Site Request Forgery)

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


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

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

## Is CVE-2026-53739 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-53739 is a medium-severity vulnerability in Yoast Duplicate Post, published on 10 Jun 2026. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2026-53739 in the wild and no public exploit code.

Affected product: Yoast Duplicate Post. 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-53739/ (Markdown: https://insights.sbomify.com/CVE-2026-53739/index.md)
```

## Sources

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

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