CVE-2026-53740
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedYoast Duplicate Post through 4.6 inserts an unescaped post title and permalink into the Classic Editor scheduled republish notice. Attackers can schedule a republish copy with a crafted title to execute script when an administrator views the resulting notice.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · high confidenceThis is a stored Cross-Site Scripting (XSS) vulnerability in the Yoast Duplicate Post WordPress plugin (versions through 4.6). The plugin fails to properly escape the post title and permalink when rendering the Classic Editor scheduled republish notice. An attacker with contributor-level or higher access can create a post with a crafted malicious title containing JavaScript code, schedule it for republishing, and achieve code execution when an administrator views the republish notice in the Classic Editor.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- Low
- User interaction
- Required
- Scope
- Changed
- Confidentiality
- Low
- Integrity
- Low
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:C/C:L/I:L/A:N
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Verify Yoast Duplicate Post is installedNavigate to Plugins > Installed Plugins in WordPress admin and locate Yoast Duplicate Post in the listAffected if Plugin is not installed - not affected
-
Identify the installed plugin versionClick on the plugin in the Plugins list to view its details, or check the plugin header in /wp-content/plugins/duplicate-post/duplicate-post.php for the Version fieldAffected if Version is 4.6 or lower (the vulnerable versions)
-
Confirm Classic Editor is activeGo to Settings > Writing and check if Classic Editor is selected, or inspect the active editor via wp-admin optionsAffected if Classic Editor mode is enabled (the vulnerability only affects Classic Editor republish notices)
-
Check for existing republish copiesReview Posts list for any entries with 'Republish' status or check the Duplicate Post settings for scheduled republishesAffected if Republish copies exist with user-generated titles that could contain malicious scripts
A site is affected if it runs Yoast Duplicate Post version 4.6 or earlier AND uses Classic Editor, with republish notice functionality enabled.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
From vendor dataUpdate Yoast Duplicate Post to the latest version (4.6+) which should contain the patched code with proper output escaping. If no update is available, consider disabling the Classic Editor republish functionality or the plugin until a fix is released.
- Consultation1.0 h
- Implementation1.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,376.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-53740 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2026-53740 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data