WP Duplicate Page <= 1.8 - Missing Authorization to Authenticated (Contributor+) Arbitrary Post Duplication
Strategic Overview
- Status
- Patched in 1.8.1
- Affected Plugin
- WP Duplicate Page
- Affected Version
<= 1.8- CVSS
- 5.4Medium
- Weakness type
- CWE-862 · Missing Authorization
- CVE
CVE-2025-14001
At a glance
CVE-2025-14001 is a medium-severity Missing Authorization vulnerability in the WP Duplicate Page WordPress plugin, affecting versions <= 1.8. It carries a CVSS score of 5.4 (reachable over the network; low attack complexity). Exploitation requires an authenticated account at Contributor level or above. The issue is fixed in version 1.8.1; sites on affected versions should update now. Disclosed January 2026, reported by Sarawut Poolkhet (MisterHelloz).
Vulnerability Overview
The WP Duplicate Page plugin for WordPress is vulnerable to unauthorized modification of data due to missing capability checks on the 'duplicateBulkHandle' and 'duplicateBulkHandleHPOS' functions in all versions up to, and including, 1.8. This makes it possible for authenticated attackers, with Contributor-level access and above, to duplicate arbitrary posts, pages, and WooCommerce HPOS orders even when their role is explicitly excluded from the plugin's "Allowed User Roles" setting, potentially exposing sensitive information and allowing duplicate fulfillment of WooCommerce orders.
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
WP Duplicate Page <= 1.8 carries this weakness at duplicateBulkHandle, 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 WP Duplicate Page the fix is 1.8.1: builds <= 1.8 are affected, anything from 1.8.1 onward is not.
Remediation
Update to version 1.8.1, 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: WP Duplicate Page 1.8.1 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 WP Duplicate Page
Vulnerability data © Defiant, Inc., provided under the Wordfence Intelligence T&C