dbcve.org
Missing AuthorizationWeakness · CWE-862

CVE-2026-8684

MEDIUM · 5.3 CVSS v3.1 Published 2026-05-22
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
62/100
Remediation priority · Elevated
Remotely reachable No privileges 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 MotoPress Hotel Booking plugin for WordPress is vulnerable to authorization bypass in all versions up to, and including, 6.0.1. This is due to the plugin not properly verifying that a user is authorized to perform an action. This makes it possible for unauthenticated attackers to overwrite or delete the internal notes (_mphb_booking_internal_notes) of any booking by supplying an arbitrary booking ID. The nonce for this action is output in the HTML source of every public page through wp_localize_script (MPHB._data.nonces), so any unauthenticated visitor can obtain a valid nonce and perform the action without any account or prior interaction.

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 MotoPress Hotel Booking plugin for WordPress (versions up to 6.0.1) contains an authorization bypass vulnerability where the plugin exposes internal action nonces in publicly accessible HTML through wp_localize_script. Unauthenticated attackers can obtain these nonces and use them to overwrite or delete internal notes (_mphb_booking_internal_notes) of any booking by supplying an arbitrary booking ID, without needing any user account or prior authentication.

MitigationUpdate the MotoPress Hotel Booking plugin to version 6.0.2 or later. As a temporary mitigation, consider disabling the plugin or restricting access to the affected endpoints until the patch can be applied.

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
None
Integrity
Low
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/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 plugin version
    In WordPress admin, go to Plugins > Installed Plugins > MotoPress Hotel Booking and note the version number displayed. Compare this version to the affected range (versions prior to 6.0.2).
    Affected if The installed version is earlier than 6.0.2.
  2. Verify plugin is active
    Confirm the MotoPress Hotel Booking plugin is activated in the WordPress plugins list.
    Affected if The plugin is active and the version is earlier than 6.0.2.
  3. Inspect page source for nonce exposure
    Visit any public page on the site that loads the MotoPress Hotel Booking functionality (such as a booking calendar or accommodation listing). View the page source (Ctrl+U or right-click > View Page Source) and search for 'MPHB' or '_data' or 'nonces' to locate the wp_localize_script output.
    Affected if The HTML contains an object like MPHB._data.nonces with visible nonce values on a public (non-authenticated) page.
  4. Check if booking internal notes feature is in use
    Log into the WordPress admin and navigate to Hotel Booking > Bookings. Look at existing bookings to see if any have content in the Internal Notes field, or check the plugin settings for whether internal notes are enabled.
    Affected if The booking system is in use and internal notes can be stored with bookings.
  5. Test AJAX endpoint accessibility
    Using a browser or HTTP tool, send a request to the site AJAX endpoint (typically /wp-admin/admin-ajax.php) with a test action related to booking notes (such as mphb_update_booking_internal_note) using an obtained nonce, specifying a booking ID.
    Affected if The AJAX request is processed without requiring authentication or proper authorization checks for the booking ID.

The environment is affected if MotoPress Hotel Booking version is earlier than 6.0.2, the plugin is active, and public pages expose nonces in the HTML source.

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 the MotoPress Hotel Booking plugin to version 6.0.2 or later. As a temporary mitigation, consider disabling the plugin or restricting access to the affected endpoints until the patch can be applied.

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation1.0 h
  • Testing2.0 h
  • Review / QA1.0 h
6.0 hours of engineering $1,060
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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