CVE-2024-13468
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 · uneditedThe Trash Duplicate and 301 Redirect plugin for WordPress is vulnerable to unauthorized loss of data due to a missing capability check on the 'duplicates-action-top' action in all versions up to, and including, 1.9. This makes it possible for unauthenticated attackers to delete arbitrary posts/pages.
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 confidenceThe Trash Duplicate and 301 Redirect WordPress plugin fails to check user capabilities before executing the 'duplicates-action-top' action, allowing any unauthenticated visitor to delete arbitrary posts or pages on the site.
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
- None
- Integrity
- High
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/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.
-
Locate the plugin versionAccess the WordPress admin dashboard under Plugins > Installed Plugins, or check the plugin directory (wp-content/plugins/trash-duplicate-and-301-redirect) for a main PHP file containing the plugin header with the Version fieldAffected if the displayed version is below 1.9 or the version field cannot be read (indicating an old release)
-
Verify version from plugin file headerOpen the primary plugin PHP file (such as trash-duplicate-and-301-redirect.php) and locate the 'Version:' comment in the file headerAffected if the version number listed is less than 1.9.0
-
Check WordPress plugin repository for version referenceIf the version is not visible in the plugin files, search the WordPress plugin repository for 'Trash Duplicate and 301 Redirect' and compare your installed version against the latest releaseAffected if the repository version is 1.9 or higher but your installed version is lower, indicating an outdated vulnerable copy
-
Confirm the vulnerable action handler exists (optional)Examine the main plugin PHP file for the 'duplicates-action-top' action hook handler - look for code that processes post/page deletion without a current_user_can() or similar capability check before the delete operationAffected if the action handler is present and contains no capability verification (no current_user_can call)
The environment is affected if the installed Trash Duplicate and 301 Redirect plugin version is below 1.9.0 and the plugin is active.
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.
dbcve · scopedUpdate the plugin to version 1.9 or later which includes the capability check fix, or disable the plugin until the patch can be applied.
Version 1.9.1 or later (latest available version)
- Log in to WordPress admin dashboard
- Navigate to Plugins > Installed Plugins
- Locate 'Trash Duplicate and 301 Redirect' plugin
- Click 'Update Now' to install the latest available version
- Verify the update completes successfully
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.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,696.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-13468 — 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-2024-13468 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