dbcve.org
Improper AuthenticationWeakness · CWE-287

CVE-2026-9830

HIGH · 8.2 CVSS v3.1 Published 2026-07-27
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
91/100
Remediation priority · Urgent
Remotely reachable No privileges Zero-click 3 weeks old

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 bookingpress-appointment-booking-pro WordPress plugin before 5.7.3 does not correctly invoke its REST permission callback, leaving every route in one of its API namespaces reachable without authentication and allowing unauthenticated attackers to read customer booking data and modify other users' bookings.

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 bookingpress-appointment-booking-pro WordPress plugin before version 5.7.3 has a broken access control vulnerability where REST API routes in one namespace lack proper permission callback enforcement, allowing any unauthenticated user to access these endpoints. Attackers can read sensitive customer booking data and modify existing bookings belonging to other users.

MitigationUpgrade the bookingpress-appointment-booking-pro plugin to version 5.7.3 or later immediately. If the site may have been compromised, audit access logs for suspicious activity and consider resetting user credentials.

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
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
Low
Availability
None

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

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. Check installed BookingPress plugin version
    Log into WordPress admin, navigate to Plugins > Installed Plugins, find BookingPress Appointment Booking, and note the version number displayed. Alternatively, open wp-content/plugins/bookingpress-appointment-booking-pro/readme.txt and check the version in the header.
    Affected if Version is lower than 5.7.3
  2. Identify the plugin API namespace
    Check the plugin main PHP file (e.g., bookingpress-appointment-booking-pro.php) for register_rest_route calls to identify the API namespace path, typically /wp-json/bookingpress/v1/ or similar.
    Affected if API namespace exists in the plugin (which it does for versions below 5.7.3)
  3. Test unauthenticated API access
    Send an HTTP GET request to the plugin's REST API endpoint without any authentication headers. For example: curl -s https://yourdomain.com/wp-json/bookingpress/v1/booking/. Observe if the server returns a successful response with booking data instead of a 401 or 403 authentication error.
    Affected if The API returns booking data or accepts the request without requiring authentication (no 401/403 error)
  4. Verify sensitive data exposure
    Examine the API response from the previous step to confirm whether customer booking information such as names, emails, phone numbers, appointment details, or booking IDs is visible in the response payload.
    Affected if Customer PII, appointment details, or booking records are exposed in the unauthenticated API response

If the plugin version is below 5.7.3 AND the REST API endpoint responds to unauthenticated requests with booking data or allows modification of bookings, the environment is affected by CVE-2026-9830.

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.

dbcve · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Upgrade the bookingpress-appointment-booking-pro plugin to version 5.7.3 or later immediately. If the site may have been compromised, audit access logs for suspicious activity and consider resetting user credentials.

Recommended fix High confidence

bookingpress-appointment-booking-pro version 5.7.3

  1. Log in to the WordPress admin dashboard
  2. Navigate to Plugins > Installed Plugins
  3. Locate the bookingpress-appointment-booking-pro plugin
  4. Verify the currently installed version is below 5.7.3
  5. If vulnerable, click Update Now to upgrade to version 5.7.3 or later
  6. After updating, confirm the new version number in the plugins list
  7. Test that booking functionality works correctly after the update

Generated from the published advisory — verify against the referenced sources before acting.

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation2.0 h
  • Testing3.0 h
  • Review / QA1.0 h
8.0 hours of engineering $1,390
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-9830 — 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-9830 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