Post Duplicator <= 3.0.11 - Authorization Bypass to Authenticated (Contributor+) Post Duplication
Strategic Overview
- Status
- Patched in 3.0.12
- Affected Plugin
- Post Duplicator
- Affected Version
<= 3.0.11- CVSS
- 4.3Medium
- Weakness type
- CWE-863 · Incorrect Authorization
- CVE
CVE-2026-4245
At a glance
CVE-2026-4245 is a medium-severity Incorrect Authorization vulnerability in the Post Duplicator WordPress plugin, affecting versions <= 3.0.11. 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.12; sites on affected versions should update now. Disclosed August 2026, reported by Quốc Huy (jtwings).
Vulnerability Overview
The Post Duplicator plugin for WordPress is vulnerable to authorization bypass in all versions up to, and including, 3.0.11. This is due to the `duplicate_post_permissions()` permission callback only verifying the `duplicate_posts` capability without checking whether the requesting user holds `publish_posts` or other status-gated capabilities. This makes it possible for authenticated attackers, with Contributor-level access and above, to create duplicate posts with `future` (scheduled, auto-publishes) or `private` status, bypassing editorial review. Additionally, the REST endpoint does not enforce administrator-configured post-type duplication restrictions, allowing duplication of post types that have been explicitly disabled.
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-863: Incorrect Authorization
Post Duplicator <= 3.0.11 carries this weakness at duplicate_post_permissions(), and reaching it takes an account at Contributor level or above. Incorrect authorization means a permission check exists but evaluates the wrong thing, so it passes for callers it was meant to stop.
The action runs for users the code intended to exclude, with the same effect as having no check at all. For Post Duplicator the fix is 3.0.12: builds <= 3.0.11 are affected, anything from 3.0.12 onward is not.
Remediation
Update to version 3.0.12, 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.12 closes this, and updating the plugin is the step that ends it.
- Login Security
- Alerts
External References
Related records
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-4244: Post Duplicator Authenticated (Contributor+) Post
CVE-2026-4244 - 4.3CVE-2026-2301: Post Duplicator Authenticated (Contributor+) Protected
CVE-2026-2301 - 4.3CVE-2025-24736: Post Duplicator <= 2.35 Missing Authorization
CVE-2025-24736 - 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