Page and Post Clone <= 6.0 - Insecure Direct Object Reference to Authenticated (Author+) Sensitive Information Exposure
Strategic Overview
- Status
- Patched in 6.1
- Affected Plugin
- Fast Page & Post Duplicator
- Affected Version
<= 6.0- CVSS
- 4.3Medium
- Weakness type
- CWE-639 · Authorization Bypass Through User-Controlled Key
- CVE
CVE-2024-5942
At a glance
CVE-2024-5942 is a medium-severity Authorization Bypass Through User-Controlled Key vulnerability in the Fast Page & Post Duplicator WordPress plugin, affecting versions <= 6.0. It carries a CVSS score of 4.3 (reachable over the network; low attack complexity). Exploitation requires an authenticated account at Author level or above. The issue is fixed in version 6.1; sites on affected versions should update now. Disclosed June 2024, reported by Bassem Essam.
Vulnerability Overview
The Page and Post Clone plugin for WordPress is vulnerable to Insecure Direct Object Reference in all versions up to, and including, 6.0 via the 'content_clone' function due to missing validation on a user controlled key. This makes it possible for authenticated attackers, with Author-level access and above, to clone and read private posts.
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-639: Authorization Bypass Through User-Controlled Key
Fast Page & Post Duplicator <= 6.0 carries this weakness at content_clone, and reaching it takes an account at Author level or above. Authorization bypass through a user-controlled key, often called insecure direct object reference, means the application looks up a record by an identifier from the request without checking that the caller owns it.
Changing a number in the request is enough to read or modify other users' records, which on commerce and membership sites means customer data. For Fast Page & Post Duplicator the fix is 6.1: builds <= 6.0 are affected, anything from 6.1 onward is not.
Remediation
Update to version 6.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: Fast Page & Post Duplicator 6.1 closes this, and updating the plugin is the step that ends it.
- Login Security
- Alerts
External References
Related records
Other vulnerabilities in Fast Page & Post Duplicator
Vulnerability data © Defiant, Inc., provided under the Wordfence Intelligence T&C