The Ultimate WordPress Toolkit – WP Extended <= 3.0.8 - Insecure Direct Object Reference
Strategic Overview
- Status
- Patched in 3.0.9
- Affected Plugin
- WP Extended – The Ultimate WordPress Toolkit
- Affected Version
<= 3.0.8- CVSS
- 5.4Medium
- Weakness type
- CWE-639 · Authorization Bypass Through User-Controlled Key
- CVE
CVE-2024-8123
At a glance
CVE-2024-8123 is a medium-severity Authorization Bypass Through User-Controlled Key vulnerability in the WP Extended WordPress plugin, affecting versions <= 3.0.8. It carries a CVSS score of 5.4 (reachable over the network; low attack complexity). The issue is fixed in version 3.0.9; sites on affected versions should update now. Disclosed September 2024, reported by Marco Wotschka.
Vulnerability Overview
The The Ultimate WordPress Toolkit – WP Extended plugin for WordPress is vulnerable to Insecure Direct Object Reference in all versions up to, and including, 3.0.8 via the duplicate_post function due to missing validation on a user controlled key. This makes it possible for authenticated attackers, with Contributor-level access and above, to duplicate posts written by other authors including admins. This includes the ability to duplicate password-protected posts, which reveals their contents.
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
Reaching this weakness in WP Extended <= 3.0.8 takes a caller who can reach the endpoint. 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 WP Extended 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: WP Extended 3.0.9 closes this, and updating the plugin is the step that ends it.
- Login Security
- Alerts
External References
Related records
Other vulnerabilities in WP Extended – The Ultimate WordPress Toolkit
- 8.8CVE-2026-4314: The Ultimate WordPress Toolkit Privilege Escalation
CVE-2026-4314 - 8.8CVE-2024-11816: The Ultimate… Authenticated (Subscriber+) RCE
CVE-2024-11816 - 8.8CVE-2024-8104: The Ultimate WordPress Toolkit Directory Traversal
CVE-2024-8104 - 8.8CVE-2024-8102: The Ultimate WordPress Toolkit Arbitrary Options Update
CVE-2024-8102 - 7.5CVE-2024-13184: The Ultimate WordPress Toolkit SQL Injection
CVE-2024-13184 - 7.4CVE-2024-11916: The Ultimate… Authenticated (Subscriber+) Stored XSS
CVE-2024-11916 - 6.5CVE-2024-8106: The Ultimate WordPress Toolkit Info Exposure
CVE-2024-8106 - 6.4CVE-2025-4963: WP Extended <= 3.0.15 Stored Cross-Site Scripting
CVE-2025-4963
Vulnerability data © Defiant, Inc., provided under the Wordfence Intelligence T&C