CVE-2026-53738: Copy & Delete Posts Authorization Bypass – WordPress Plugin Vulnerability
Copy & Delete Posts, a WordPress plugin, contains a critical authorization flaw that allows any user with a plugin-enabled role—even non-administrators—to perform privileged operations they shouldn't be able to access. Through a parameter called 'f', attackers can delete posts or change plugin configuration settings. The vulnerability stems from missing per-function permission checks in the plugin's AJAX handler, meaning the plugin trusts user input without verifying what actions each user is authorized to perform.
Source data · NVD / CISA · public domain
- CVSS
- 3.1 · 8.1 HIGH · CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:H/A:H
- Weaknesses (CWE)
- CWE-863
- Affected products
- 0 configuration(s)
- Published / Modified
- 2026-06-10 / 2026-06-17
NVD description (verbatim)
Copy & Delete Posts through 1.5.4 lets any plugin-enabled non-admin role invoke every operation in the cdp_action_handling AJAX handler. Attackers with an enabled role can delete posts or overwrite plugin settings via the f parameter, bypassing per-function capability checks.
2 reference(s) · View on NVD →
SEC.co analysis · AI-assisted, reviewed against source
Technical summary
CVE-2026-53738 is an authorization bypass vulnerability in Copy & Delete Posts through version 1.5.4. The plugin's cdp_action_handling AJAX handler fails to implement function-level authorization controls, relying instead on a single role-based gate that permits any plugin-enabled non-admin user to invoke all supported operations. The 'f' parameter is used to specify which action to execute; the handler lacks per-function capability checks (mapped to CWE-863, Incorrect Authorization). This allows authenticated users with minimal privileges to invoke delete and settings-modification functions reserved for administrators.
Business impact
Organizations using Copy & Delete Posts face direct threats to content integrity and operational continuity. Attackers with any enabled non-admin role can systematically delete posts, disrupting published content and potentially damaging SEO, user trust, and workflow. Plugin settings can be overwritten, potentially disabling security features, exfiltrating configuration data, or establishing persistence. The impact scales with the number of users assigned plugin-enabled roles; every such account becomes a potential attack surface. This is especially severe for multisite deployments or agencies managing many WordPress instances with delegated user roles.
Affected systems
Copy & Delete Posts version 1.5.4 and earlier are affected. The plugin is installed on any WordPress site where it is active and at least one non-administrator user has been granted a role that enables the plugin. No fixed version has been published by the vendor as of this advisory's modification date (June 17, 2026). Organizations should verify their installed version and review which user roles have plugin activation capability.
Exploitability
This vulnerability is highly exploitable. It requires only network access and valid WordPress credentials for any role with plugin activation enabled—a common configuration in multisite or agency environments. No user interaction, complex exploitation steps, or zero-day techniques are needed; the flaw is trivial to trigger via standard AJAX calls. The CVSS 3.1 score of 8.1 (HIGH) reflects the low attack complexity and high impact on integrity and availability. Non-KEV status should not diminish concern; the simplicity of exploitation and ease of chaining with other WordPress compromises make this a prioritized target.
Remediation
Immediately disable or deactivate the Copy & Delete Posts plugin on all affected WordPress installations. If the plugin is critical to operations, restrict its use to administrator accounts only and monitor AJAX logs for unauthorized cdp_action_handling requests. The vendor has not released a patched version; remediation currently requires either removal or applying a custom capability-checking patch (if in-house expertise is available). Contact the plugin maintainers to request a security update or consider switching to an alternative, maintained plugin with proper authorization controls.
Patch guidance
As of the modification date (June 17, 2026), no official patch has been released by the Copy & Delete Posts vendor. Do not assume a patch is available; verify the official plugin repository or vendor advisory before upgrading. If you are aware of a patched version, confirm it directly against the vendor's security page. In the interim, deactivate the plugin or restrict it to administrator roles only via WordPress' role management system. If custom development is feasible, ensure all functions in the cdp_action_handling handler perform explicit capability checks before executing user-requested operations.
Detection guidance
Monitor WordPress AJAX logs for requests to admin-ajax.php with the action parameter set to 'cdp_action_handling'. Log all POST requests that include the 'f' parameter (which specifies the function to execute) and cross-reference the requesting user's role against the intended operation—privilege escalation attempts will show non-admin users invoking 'delete' or 'settings' functions. Enable WordPress audit logging or use a Web Application Firewall (WAF) to flag unexpected AJAX patterns. Search your site's activity logs for patterns of post deletion or settings changes by non-administrator accounts, which may indicate exploitation.
Why prioritize this
This vulnerability merits urgent patching priority due to its high CVSS score (8.1), ease of exploitation, direct impact on post and plugin integrity, and lack of compensating controls in typical WordPress deployments. The absence of per-function authorization is a fundamental flaw that can be exploited by any non-admin user, making it likely to be weaponized in targeted attacks or used as part of supply-chain compromises against WordPress sites. The fact that it is not yet in the CISA KEV catalog should not delay action; the simplicity of the vulnerability ensures eventual public exploitation.
Risk score, explained
The CVSS 3.1 score of 8.1 reflects a network-accessible vulnerability with low attack complexity, requiring only a single valid (low-privilege) credential. The impact on integrity (high—posts and settings can be modified) and availability (high—posts can be deleted) drives the severity. Confidentiality impact is none because data is not exfiltrated. The score accurately represents the real-world danger to WordPress operators relying on role-based access controls, though the practical risk is heightened by the plugin's common use in multisite and agency settings where multiple non-admin users are routine.
Frequently asked questions
Can this vulnerability be exploited without WordPress credentials?
No. The vulnerability requires valid WordPress user credentials for a role that has the Copy & Delete Posts plugin enabled. However, such roles are often granted liberally in multisite and agency environments, making the barrier to exploitation low. If your site uses default contributor or editor roles, they may already have plugin activation permissions.
Does deactivating the plugin protect an already-compromised site?
Deactivating the plugin stops new exploitation, but it does not undo past damage. Any posts or settings deleted or modified before deactivation will remain altered. Review post revision history and database backups to identify what was changed, and restore from a known-good backup if compromise is suspected.
Is there a way to mitigate this without removing the plugin?
Yes, temporarily: restrict plugin activation to administrators only via WordPress role management, monitor AJAX logs, and regularly audit non-admin user accounts and their actions. However, this is a temporary measure. You should aggressively pursue either an official patch from the vendor or replacement with a security-vetted alternative plugin.
Will installing a Web Application Firewall (WAF) block this attack?
A WAF can help by rate-limiting AJAX requests or flagging suspicious patterns, but it cannot reliably block every exploitation attempt without risking false positives. A WAF is a useful secondary control, but the primary remediation is to remove or patch the vulnerable plugin.
This advisory is based on vulnerability data published as of June 17, 2026. Vendor patch information and exploitation status may change; verify against the official plugin repository and CISA KEV catalog before making deployment decisions. No proof-of-concept exploit code is provided. Organizations should conduct their own risk assessment and consult with their security teams before implementing remediation. SEC.co makes no warranty regarding the completeness or accuracy of exploit information or vendor patch status; this document is for informational purposes only. Source: NVD (public-domain), retrieved 2026-07-20. Analysis generated by SEC.co (claude-haiku-4-5).
Weaknesses (CWE)
Related vulnerabilities
- CVE-2016-20075HIGHWordPress Ultimate Product Catalog 3.8.6 Arbitrary File Upload (CVSS 8.8)
- CVE-2025-14774HIGHABB T-MAC Plus Denial-of-Service Vulnerability (CVSS 7.4)
- CVE-2025-32348HIGHAndroid Local Privilege Escalation via Missing Permission Check
- CVE-2026-0272HIGHPalo Alto PAN-OS Privilege Escalation Vulnerability (PA-Series, VM-Series, Panorama)
- CVE-2026-21031HIGHAppBlock Authorization Flaw in Samsung Android—Risk & Patch Guidance
- CVE-2026-24724HIGHQNAP File Station 6 Authorization Bypass (CVSS 8.1)
- CVE-2026-3514HIGHPrefect 3.6.19 Authentication Bypass via Health Check Exemptions
- CVE-2026-35482HIGHalf.io Sandbox Escape Allows Admin Command Execution