CVE-2026-16298

FoodBoxBooker <= 1.0.6 - Privilege Escalation to Unauthenticated Arbitrary Password Reset

2026-08-05 00:00
moonge

Strategic Overview

Status
Patched in 1.0.7
Affected Plugin
FoodBoxBooker
Affected Version
<= 1.0.6
CVSS
7.3High
Weakness type
CWE-269 · Improper Privilege Management
CVE
CVE-2026-16298
View all FoodBoxBooker vulnerabilities

At a glance

CVE-2026-16298 is a high-severity Improper Privilege Management vulnerability in the FoodBoxBooker WordPress plugin, affecting versions <= 1.0.6. It carries a CVSS score of 7.3 (reachable over the network; low attack complexity). Exploitation requires no authentication. The issue is fixed in version 1.0.7; sites on affected versions should update now. Disclosed August 2026, reported by moonge.

Vulnerability Overview

The FoodBoxBooker plugin for WordPress is vulnerable to Privilege Escalation in versions up to, and including, 1.0.6. This is due to missing authentication check on the wp_ajax_nopriv_account_edit_formsubmit action and reliance on a user-supplied fbbttm-userid POST parameter instead of the current authenticated user's ID. This makes it possible for unauthenticated attackers to reset any user's password without authentication by supplying an arbitrary user ID via the account edit form submission endpoint.

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 privileges on the target site, and no interaction from a victim user.

CWE-269: Improper Privilege Management

Reaching this weakness in FoodBoxBooker <= 1.0.6 takes no account at all. Improper privilege management means the code lets an account end up with capabilities its role should not have.

It converts a low-privileged account into an administrative one, which makes every other restriction on the site irrelevant. For FoodBoxBooker the fix is 1.0.7: builds <= 1.0.6 are affected, anything from 1.0.7 onward is not.

Remediation

Update to version 1.0.7, or a newer patched version

How does WordSec protect against this?

This one needs no account at all, which puts it outside what login hardening can reach; WordSec's login security narrows the account-level paths around it, and the firewall is what inspects the request itself. None of that substitutes for the fix: FoodBoxBooker 1.0.7 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