dbcve.org
Missing AuthorizationWeakness · CWE-862

CVE-2026-1217

MEDIUM · 5.4 CVSS v3.1 Published 2026-03-18
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
60/100
Remediation priority · Elevated
Remotely reachable Zero-click

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 · unedited
The Yoast Duplicate Post plugin for WordPress is vulnerable to unauthorized modification of data due to a missing capability check on the clone_bulk_action_handler() and republish_request() functions in all versions up to, and including, 4.5. This makes it possible for authenticated attackers, with Contributor-level access and above, to duplicate any post on the site including private, draft, and trashed posts they shouldn't have access to. Additionally, attackers with Author-level access and above can use the Rewrite & Republish feature to overwrite any published post with their own content.

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 confidence

The Yoast Duplicate Post plugin lacks capability checks on clone_bulk_action_handler() and republish_request() functions, allowing any authenticated Contributor+ user to duplicate posts they shouldn't access (private, draft, trashed), and Authors+ to overwrite published posts via the Rewrite & Republish feature.

MitigationUpdate to the latest version of Yoast Duplicate Post (4.6 or later) which implements proper capability checks; alternatively, disable the plugin until patched.

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
None
Scope
Unchanged
Confidentiality
Low
Integrity
Low
Availability
None

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/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 checks

Work through these to decide whether this CVE applies to you.

  1. Verify Yoast Duplicate Post plugin is installed
    In WordPress admin, go to Plugins > Installed Plugins and look for 'Yoast Duplicate Post' in the list. Alternatively, check the /wp-content/plugins/ directory for a folder named 'duplicate-post'
    Affected if The plugin appears in the installed plugins list
  2. Identify the installed plugin version
    In WordPress admin, go to Plugins > Installed Plugins and locate Yoast Duplicate Post. The version number is displayed below the plugin name. Alternatively, check the plugin's main PHP file header for the 'Version' tag
    Affected if The version is lower than 4.6 or cannot be determined (plugin is present but version is unlisted)
  3. Confirm active user accounts with Contributor role
    In WordPress admin, go to Users > All Users and review the Role column. Identify any users assigned the Contributor role
    Affected if At least one user with Contributor role exists and the plugin is vulnerable
  4. Confirm active user accounts with Author role
    In WordPress admin, go to Users > All Users and review the Role column. Identify any users assigned the Author role
    Affected if At least one user with Author role exists and the plugin is vulnerable
  5. Check if duplicate/republish features are accessible to lower-privileged users
    Attempt to access the plugin settings or use the duplicate post functionality while logged in as a Contributor-level user. Verify whether the bulk clone action or Rewrite & Republish option is available
    Affected if A Contributor can access bulk clone functionality, or an Author can access the Rewrite & Republish feature on published posts

The environment is affected if Yoast Duplicate Post plugin is installed with a version below 4.6 and any Contributor or Author user accounts exist with access to the plugin's duplicate or republish features.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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.

dbcve · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Update to the latest version of Yoast Duplicate Post (4.6 or later) which implements proper capability checks; alternatively, disable the plugin until patched.

Recommended fix Moderate confidence

Version 4.5.1 or later (check wordpress.org for current latest release)

  1. Log in to WordPress admin dashboard
  2. Navigate to Plugins > Installed Plugins
  3. Find 'Yoast Duplicate Post' in the plugin list
  4. Check if current version is 4.5 or below
  5. If vulnerable, click 'Update Now' to update to the latest version
  6. Alternatively, download the latest version from wordpress.org/plugins/duplicate-post/ and upload via Plugins > Add New > Upload Plugin
  7. After update, verify the version number reflects the patched release

Generated from the published advisory — verify against the referenced sources before acting.

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA1.0 h
10.0 hours of engineering $1,750
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,800.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-1217 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-1217 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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