FoodBoxBooker <= 1.0.7 - Insecure Direct Object Reference to Authenticated (Subscriber+) Arbitrary User Profile Update
Strategic Overview
- Status
- Patched in 1.0.8
- Affected Plugin
- FoodBoxBooker
- Affected Version
<= 1.0.7- CVSS
- 4.3Medium
- Weakness type
- CWE-639 · Authorization Bypass Through User-Controlled Key
- CVE
CVE-2026-18200
At a glance
CVE-2026-18200 is a medium-severity Authorization Bypass Through User-Controlled Key vulnerability in the FoodBoxBooker WordPress plugin, affecting versions <= 1.0.7. It carries a CVSS score of 4.3 (reachable over the network; low attack complexity). Exploitation requires an authenticated account at Subscriber level or above. The issue is fixed in version 1.0.8; sites on affected versions should update now. Disclosed August 2026, reported by Erwan LR.
Vulnerability Overview
The FoodBoxBooker plugin for WordPress is vulnerable to Insecure Direct Object Reference in versions up to, and including, 1.0.7. This is due to missing authorization check on the user-controlled `fbbttm-userid` POST parameter used as the target ID in wp_update_user. This makes it possible for authenticated attackers, with subscriber-level access and above, to update arbitrary user profiles by supplying a different user ID, potentially including administrator accounts.
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 FoodBoxBooker <= 1.0.7 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 FoodBoxBooker the fix is 1.0.8: builds <= 1.0.7 are affected, anything from 1.0.8 onward is not.
Remediation
Update to version 1.0.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: FoodBoxBooker 1.0.8 closes this, and updating the plugin is the step that ends it.
- Login Security
- Alerts
External References
Related records
Other vulnerabilities in FoodBoxBooker
Vulnerability data © Defiant, Inc., provided under the Wordfence Intelligence T&C