Post Duplicator <= 3.0.8 - Missing Authorization to Authenticated (Contributor+) Protected Post Meta Insertion via 'customMetaData' Parameter
Strategic Overview
- Status
- Patched in 3.0.9
- Affected Plugin
- Post Duplicator
- Affected Version
<= 3.0.8- CVSS
- 4.3Medium
- Weakness type
- CWE-862 · Missing Authorization
- CVE
CVE-2026-2301
At a glance
CVE-2026-2301 is a medium-severity Missing Authorization vulnerability in the Post Duplicator WordPress plugin, affecting versions <= 3.0.8. It carries a CVSS score of 4.3 (reachable over the network; low attack complexity). Exploitation requires an authenticated account at Contributor level or above. The issue is fixed in version 3.0.9; sites on affected versions should update now. Disclosed February 2026, reported by bashu.
Vulnerability Overview
The Post Duplicator plugin for WordPress is vulnerable to unauthorized arbitrary protected post meta insertion in all versions up to, and including, 3.0.8. This is due to the `duplicate_post()` function in `includes/api.php` using `$wpdb->insert()` directly to the `wp_postmeta` table instead of WordPress's standard `add_post_meta()` function, which would call `is_protected_meta()` to prevent lower-privileged users from setting protected meta keys (those starting with `_`). This makes it possible for authenticated attackers, with Contributor-level access and above, to inject arbitrary protected post meta keys such as `_wp_page_template`, `_wp_attached_file`, and other sensitive meta keys on duplicated posts via the `customMetaData` JSON array parameter in the `/wp-json/post-duplicator/v1/duplicate-post` REST API endpoint.
Technical Analysis
The vector marks this flaw as remotely reachable over the network, with low attack complexity — no special timing or configuration is needed, and no interaction from a victim user.
CWE-862: Missing Authorization
Post Duplicator <= 3.0.8 carries this weakness at duplicate_post(), and reaching it takes an account at Contributor level or above. A missing authorization check means a function is reachable by anyone who can reach the endpoint, because the code never asks whether the caller is allowed to perform the action.
Any user who can reach the endpoint gets to run an action reserved for higher-privileged roles, from reading protected data to changing settings or content. For Post Duplicator the fix is 3.0.9: builds <= 3.0.8 are affected, anything from 3.0.9 onward is not.
Remediation
Update to version 3.0.9, or a newer patched version
How does WordSec protect against this?
Because it turns on account access, WordSec's login security is the relevant layer: role-based two-factor, captcha and brute-force limits raise the cost of getting the account this needs. None of that substitutes for the fix: Post Duplicator 3.0.9 closes this, and updating the plugin is the step that ends it.
- Login Security
- Alerts
External References
Related records
Same weakness class
Other vulnerabilities in Post Duplicator
- 7.5CVE-2026-10749: Post Duplicator < 3.0.15 PHP Object Injection
CVE-2026-10749 - 7.5CVE-2026-39474: Post Duplicator <= 3.0.10 PHP Object Injection
CVE-2026-39474 - 6.4CVE-2021-33852: Post Duplicator <= 2.23 Cross-Site Scripting
CVE-2021-33852 - 6.1CVE-2016-15027: Post Duplicator <= 2.16 Reflected Cross-Site Scripting
CVE-2016-15027 - 4.3CVE-2026-4245: Post Duplicator Authorization Bypass
CVE-2026-4245 - 4.3CVE-2024-12472: Post Duplicator <= 2.36 Protected Post Disclosure
CVE-2024-12472
Vulnerability data © Defiant, Inc., provided under the Wordfence Intelligence T&C