Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain
-
AccessAuthenticate as plugin-authorized WordPress user
-
DeliveryIdentify target post IDs via site enumeration
-
ExploitCraft bulk delete request with arbitrary post IDs
-
ExecutionSubmit request bypassing per-object auth check
-
ImpactPermanently delete victims' posts site-wide
Vulnerability Assessment
| Weakness |
CWE
OWASP Top 10:2025
A01:2025 - Broken Access Control
ASVS 5.0
V8 - Authorization Object-level authorization, IDOR prevention
|
| Exploitation Conditions | Exploitation requires two conditions: (1) the target WordPress site must have the Duplicate Post plugin installed and active in a version before 1.5.5, and (2) the attacker must be an authenticated WordPress user whose role has been explicitly granted plugin access by an administrator via the plugin's role-access configuration settings. Sites where only the Administrator role has plugin access are not exploitable by lower-privilege users. Sites with no backups face irreversible content loss. Exploitation is limited by the requirement for authenticated contributor-level access - unauthenticated attackers and users on sites where the plugin is restricted to admins only are not affected. There is no user interaction or social engineering component once plugin access is established. |
| Impact | The official CVSS 3.1 score of 6.5 with vector AV:N/AC:L/PR:H/UI:N/S:U/C:N/I:H/A:H assigns PR:H (High Privileges), which may understate real-world risk. The description states the flaw is exploitable by 'any user whose role an administrator has granted plugin access,' which in practice often includes Author and Editor roles - mapping to PR:L in CVSS terms, not PR:H. At PR:L, the base score would rise to approximately 8.1. EPSS at 0.13% (3rd percentile) is low and consistent with the absence from CISA KEV, suggesting no opportunistic or widespread exploitation campaigns have been observed. However, a public POC is confirmed by WPScan, which lowers the skill barrier for exploitation. The non-reversible nature of permanent post deletion (without backups) amplifies the practical impact on multi-author WordPress sites. Risk is highest on sites with multiple contributor/author-level users who have been granted plugin access, and lowest on single-author sites or installations where only administrators use the plugin. The CVSS confidentiality impact (C:N) is correctly assessed - this is a destruction/integrity attack with no data exfiltration component. |
| Exploit ScenarioDerived | An authenticated WordPress user with Author-level access on a multi-contributor news or blog site - whose role the administrator has configured to use the Duplicate Post plugin - crafts bulk delete requests substituting post IDs belonging to editors or administrators. Leveraging the publicly available POC documented by WPScan, the attacker iterates through post IDs, permanently deleting arbitrary published content across the site before the action is detected. Without a recent backup, content is unrecoverable. |
Get an e-mail when this CVE is exploited, patched or re-scored. Free account.
Alert meAnalysisAIv1 – Aug 11, 2026
Duplicate Post WordPress plugin before version 1.5.5 contains an IDOR flaw (CWE-639) in its bulk copy and delete operations that enables authenticated users with plugin-level access to permanently delete arbitrary posts across the entire site, including content owned by other users. The missing per-object authorization check means that any WordPress user role an administrator has configured to use the plugin can bypass ownership boundaries and destroy content they did not create. A publicly available proof-of-concept exists per WPScan, though EPSS at 0.13% (3rd percentile) and absence from CISA KEV indicate no confirmed widespread exploitation at time of analysis.
RemediationAI
Update the Duplicate Post WordPress plugin to version 1.5.5 or later, which contains the vendor-released fix per the CVE description and EUVD-2026-55000; consult the WPScan advisory at https://wpscan.com/vulnerability/dcced434-f7c0-4e19-b3cb-8196f6636aa3/ for confirmation. If immediate upgrade is not possible, administrators should navigate to the plugin's role-access settings and remove plugin access from any non-administrator roles until patching is complete - the trade-off being that those users will lose the ability to duplicate posts during the interim period. Additionally, ensure site backups are current and tested, since post deletion via this flaw is permanent without a restore point. No network-layer control is effective as a workaround because the requests originate from authenticated sessions over standard WordPress admin channels.
Affected VersionsENISA
Affected Packages
Source: OSV (Open Source Vulnerabilities)
Affects your stack
Affects 1 package in euvd
Checking this CVE against your own stacks and servers is part of the Basic plan and up.
Technical ContextAI · show details
The root cause is CWE-639 (Authorization Bypass Through User-Controlled Key), the classic IDOR pattern: WordPress plugins performing bulk operations on posts must enforce two distinct checks - whether the user has capability to use the feature, and whether the user has rights to each specific post object being acted upon. The Duplicate Post plugin applies role-level capability checks but omits per-object ownership validation, allowing a user-controlled post ID parameter in bulk copy and delete requests to reference posts beyond the user's legitimate scope. The affected product is identified by CPE cpe:2.3:a:unknown:duplicate_post:*:*:*:*:*:*:*:*, covering all releases from 0 up to but not including 1.5.5. The WordPress REST or admin-ajax surface used for these bulk operations processes the object key without re-verifying authorship or edit permissions against the requesting user.
Know when Duplicate Post gets its next vulnerability
- Watch products and get an email when something new is published
- Check this CVE against your own stack and servers
- Exploit and PoC references, threat intelligence from 22 sources
No credit card · 7-day full trial
Severity by source
AV:N/AC:L/PR:H/UI:N/S:U/C:N/I:H/A:H
PR:L rather than PR:H because the description allows any role granted plugin access, which typically includes low-privilege roles like Author or Editor.
Primary rating from Vendor (WPScan).
CVSS VectorVendor: WPScan
Lifecycle Timeline
4DescriptionCVE.org
The Duplicate Post WordPress plugin before 1.5.5 does not perform per-object authorisation checks in its bulk copy and delete operations, allowing any user whose role an administrator has granted Duplicate Post WordPress plugin before 1.5.5 access to permanently delete arbitrary posts on the site, including those belonging to other users.
Threat Intelligence Overview
How this decision was reached
The engine reads each signal below and applies a fixed list of rules from top to bottom. The first rule that matches sets the recommended action – like a statement, every line is shown.
What every action level means
SSVC AssessmentENISA
Priority Score
Attack Technique
Authentication bypass attacks exploit flaws in the verification mechanisms that control access to systems and applications.
More in Duplicate Post
View allThe "Duplicate Post" WordPress plugin up to and including version 1.1.9 is vulnerable to SQL Injection. Rated high sever
Several plugins for WordPress by Inisev are vulnerable to Cross-Site Request Forgery to unauthorized installation of plu
Unauthorized post data disclosure in the Duplicate Post WordPress plugin before 1.5.6 allows authenticated users holding
Duplicate Post WordPress plugin before 1.5.6 exposes password-protected post content to authenticated users who lack rea
Stored cross-site scripting in the WordPress plugin Duplicate Post (copy-delete-posts) through version 1.5.6 lets an aut
Several plugins for WordPress by Inisev are vulnerable to unauthorized installation of plugins due to a missing capabili
EUVD-2026-55000
GHSA-47f8-4hph-5246
NVD
CVE.org
EPSS
VulDB
Exploit-DB