dbcve.org
Missing AuthorizationWeakness · CWE-862

CVE-2025-13404

MEDIUM · 5.3 CVSS v3.1 Published 2025-11-25
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
62/100
Remediation priority · Elevated
Remotely reachable No privileges 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 atec Duplicate Page & Post plugin for WordPress is vulnerable to unauthorized post duplication due to missing authorization validation on the duplicate_post() function in all versions up to, and including, 1.2.20. This makes it possible for authenticated attackers, with Contributor-level access and above, to duplicate arbitrary posts, including private and password-protected posts, leading to data exposure.

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 atec Duplicate Page & Post WordPress plugin up to version 1.2.20 lacks proper authorization validation in its duplicate_post() function, allowing any authenticated user with Contributor-level access or higher to duplicate arbitrary posts including private and password-protected content.

MitigationUpdate to version 1.2.21 or later which implements proper authorization checks; if immediate update is not possible, restrict plugin access permissions or disable the plugin until the patch can be applied.

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

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/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. Identify if the atec Duplicate Page & Post plugin is installed
    In WordPress admin, go to Plugins > Installed Plugins and look for 'atec Duplicate Page & Post' or check the plugin files in wp-content/plugins/ for a directory named 'atec-duplicate-page-post' or similar
    Affected if The plugin is installed and active in WordPress
  2. Determine the installed plugin version
    In WordPress admin, go to Plugins > Installed Plugins, find the atec Duplicate Page & Post plugin, and read the version number displayed below the plugin name
    Affected if The version number is 1.2.20 or lower
  3. Verify WordPress user roles with access
    Go to Users > All Users in WordPress admin and review the roles assigned to each user; specifically identify users with Contributor, Author, Editor, or Administrator roles
    Affected if There is at least one user with Contributor-level access or higher who can access the plugin functionality
  4. Confirm the duplicate_post function is accessible
    Check if the plugin registers a REST API endpoint or admin action for duplication that can be triggered without elevated privileges; typical paths include /wp-json/atec-duplicate/v1/duplicate or admin-ajax.php with action=atec_duplicate_post
    Affected if The duplicate function is reachable by authenticated users without proper capability checks
  5. Check for private or password-protected content
    Review existing posts in Posts > All Posts and note any posts with 'Private' visibility or password protection
    Affected if Private or password-protected posts exist and the plugin version is vulnerable, allowing unauthorized duplication

A user is affected if the atec Duplicate Page & Post plugin version is 1.2.20 or lower and there are users with Contributor-level access or higher in the WordPress environment.

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 version 1.2.21 or later which implements proper authorization checks; if immediate update is not possible, restrict plugin access permissions or disable the plugin until the patch can be applied.

Recommended fix High confidence

Version 1.2.21 or later of the atec Duplicate Page & Post plugin

  1. 1. Log in to the WordPress admin dashboard
  2. 2. Navigate to Plugins > Installed Plugins
  3. 3. Locate the 'atec Duplicate Page & Post' plugin
  4. 4. If an update is available, click 'Update Now' to upgrade to the latest version
  5. 5. Verify the plugin has been updated to version 1.2.21 or later
  6. 6. Test that the duplicate functionality works correctly for authorized users

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

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation3.0 h
  • Testing3.0 h
  • Review / QA2.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-2025-13404 — 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-2025-13404 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