dbcve.org
Authorization Bypass (IDOR)Weakness · CWE-639

CVE-2026-9851

HIGH · 7.2 CVSS v3.1 Published 2026-06-06
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
78/100
Remediation priority · High
Remotely reachable Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
The Booking Package plugin for WordPress is vulnerable to Privilege Escalation via Account Takeover in versions up to, and including, 1.7.16. This is due to a missing capability check on the 'updateUser' branch of the package_app_action AJAX endpoint, where the handler only validates a nonce and the dispatcher invokes Schedule::updateUser() with the $administrator argument hard-coded to 1, bypassing the only owner-restriction check inside that function and allowing the target user to be determined solely by attacker-supplied input passed directly to wp_update_user(). This makes it possible for authenticated attackers, with Editor-level access and above, to change the email address and password of any account, including Administrator accounts, resulting in a full site takeover.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

The Booking Package plugin's AJAX endpoint 'package_app_action' missing capability checks on the 'updateUser' branch. The handler only validates a nonce but not user permissions, and Schedule::updateUser() is called with $administrator hardcoded to 1, bypassing internal owner restrictions. Attacker-supplied input passes directly to wp_update_user(), allowing authenticated Editors+ to change any user's email and password, including Administrators.

MitigationUpdate to version 1.7.17 or later. Until patched, implement server-side capability checks (manage_options) on the AJAX handler and add authorization validation before wp_update_user() calls.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
High
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:H

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Confirm Booking Package plugin is installed
    Navigate to WordPress admin > Plugins and check if 'Booking Package' appears in the installed plugins list, or inspect the directory /wp-content/plugins/ for a booking-package folder
    Affected if The Booking Package plugin directory exists in the WordPress installation
  2. Determine the installed version of Booking Package
    In WordPress admin > Plugins page, locate Booking Package and read the version number displayed under the plugin name, or open /wp-content/plugins/booking-package/booking-package.php and check the Version header in the plugin comment block
    Affected if The reported version is 1.7.16 or any version up to and including 1.7.16
  3. Verify the plugin is active
    In WordPress admin > Plugins, check if Booking Package shows as 'Active' under its status column, or query the WordPress options table for the active_plugins option
    Affected if The plugin is activated on the WordPress site
  4. Check for users with Editor role or higher
    In WordPress admin > Users, review the list of users and their assigned roles. Note any accounts with Editor, Author, Contributor, or Administrator roles that are not the current admin account
    Affected if Multiple users exist with Editor-level access or higher, providing potential attackers with the required privilege level

The environment is affected if Booking Package plugin version 1.7.16 or earlier is installed and active on WordPress, and any user account with Editor or higher role exists in the system.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

From vendor data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Update to version 1.7.17 or later. Until patched, implement server-side capability checks (manage_options) on the AJAX handler and add authorization validation before wp_update_user() calls.

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA2.0 h
11.0 hours of engineering $1,930
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,088.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-9851 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-9851 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data