WP FEvents Book <= 0.46 - Authenticated (Subscriber+) Insecure Direct Object Reference to Booking Manipulation
Strategic Overview
- Status
- Patched in 0.47
- Affected Plugin
- WP FEvents Book
- Affected Version
<= 0.46- CVSS
- 6.3Medium
- Weakness type
- CWE-639 · Authorization Bypass Through User-Controlled Key
- CVE
CVE-2023-1129
At a glance
CVE-2023-1129 is a medium-severity Authorization Bypass Through User-Controlled Key vulnerability in the WP FEvents Book WordPress plugin, affecting versions <= 0.46. It carries a CVSS score of 6.3 (reachable over the network; low attack complexity). Exploitation requires an authenticated account at Subscriber level or above. The issue is fixed in version 0.47; sites on affected versions should update now. Disclosed April 2023, reported by Ameen Alkurdy.
Vulnerability Overview
The WP FEvents Book plugin for WordPress is vulnerable to unauthorized access of data, modification of data, and loss of data due to insufficient controls on the userID controlled via the showform_fevent6 function in versions up to, and including, 0.46. This makes it possible for authenticated attackers, with minimal permissions such as a subscriber, to manipulate booking data for any user.
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 FEvents Book <= 0.46 takes an account at Subscriber 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 WP FEvents Book the fix is 0.47: builds <= 0.46 are affected, anything from 0.47 onward is not.
Remediation
Update to version 0.47, 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 FEvents Book 0.47 closes this, and updating the plugin is the step that ends it.
- Login Security
- Alerts
External References
Related records
Other vulnerabilities in WP FEvents Book
Vulnerability data © Defiant, Inc., provided under the Wordfence Intelligence T&C