WP Duplicate Page <= 1.7 - Missing Authorization to Authenticated (Contributor+) Sensitive Information Disclosure
Strategic Overview
- Status
- Patched in 1.8
- Affected Plugin
- WP Duplicate Page
- Affected Version
<= 1.7- CVSS
- 4.3Medium
- Weakness type
- CWE-862 · Missing Authorization
- CVE
CVE-2025-12481
At a glance
CVE-2025-12481 is a medium-severity Missing Authorization vulnerability in the WP Duplicate Page WordPress plugin, affecting versions <= 1.7. 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 1.8; sites on affected versions should update now. Disclosed November 2025, reported by Athiwat Tiprasaharn (Jitlada).
Vulnerability Overview
The WP Duplicate Page plugin for WordPress is vulnerable to Missing Authorization in all versions up to, and including, 1.7. This is due to the plugin not properly verifying that a user is authorized to perform an action in the 'saveSettings' function. This makes it possible for authenticated attackers, with Contributor-level access and above, to modify plugin settings that control role capabilities, and subsequently exploit the misconfigured capabilities to duplicate and view password-protected posts containing sensitive information.
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.7 carries this weakness at saveSettings, 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: builds <= 1.7 are affected, anything from 1.8 onward is not.
Remediation
Update to version 1.8, 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 closes this, and updating the plugin is the step that ends it.
- Login Security
- Alerts
External References
Related records
Other vulnerabilities in WP Duplicate Page
Vulnerability data © Defiant, Inc., provided under the Wordfence Intelligence T&C