dbcve.org
Cross-site Scripting (XSS)Weakness · CWE-79

CVE-2026-42751

MEDIUM · 6.5 CVSS v3.1 Published 2026-05-27
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
69/100
Remediation priority · Elevated
Remotely reachable

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
Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting') vulnerability in wpdevelop Booking Manager booking-manager allows Stored XSS.This issue affects Booking Manager: from n/a through <= 2.1.18.

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

A stored XSS vulnerability in wpdevelop Booking Manager plugin allows authenticated attackers to inject malicious JavaScript code through unsanitized input fields in booking forms. The payload persists in the database and executes when administrative users or other visitors view booking management pages.

MitigationUpdate to the latest version of Booking Manager if a patch is available. Otherwise, implement proper input validation and output encoding on all booking form fields, particularly those that accept user-provided data and are displayed back in the admin dashboard or booking confirmation pages.

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
Low
User interaction
Required
Scope
Changed
Confidentiality
Low
Integrity
Low
Availability
Low

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

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. Identify Booking Manager plugin installation
    In WordPress admin, go to Plugins > Installed Plugins and locate 'Booking Manager' or 'wpdevelop Booking Manager'. Note the installed version number displayed there.
    Affected if The plugin is installed and the version is lower than the patched version (if known) or cannot be determined to be current.
  2. Verify user registration is enabled
    Go to WordPress Settings > General > Membership and check if 'Anyone can register' is enabled. Also check if low-privileged user accounts (subscribers, customers) can be created.
    Affected if User registration is open or low-privilege accounts can be created, allowing authenticated attackers to access booking forms.
  3. Confirm booking form accessibility
    Visit the public booking form pages on your site. Determine if they are accessible to logged-in users with subscriber-level or customer-level privileges, or if anonymous submissions are accepted.
    Affected if Booking forms accept input from authenticated users below administrator level or from anonymous visitors.
  4. Inspect database for suspicious payloads
    Access your WordPress database (via phpMyAdmin or CLI) and examine tables related to bookings (commonly named like wp_bk_booking, wp_booking, or similar). Search for script tags, iframe tags, or javascript: protocols in text fields.
    Affected if Database records contain unsanitized HTML or JavaScript code such as <script>, <img onerror=, or javascript: URLs in booking-related fields.
  5. Review booking management pages
    Log in as an administrator and navigate to the Booking Manager admin pages where bookings are listed or details are displayed. Observe if booking data renders without proper encoding in the admin dashboard.
    Affected if Booking information displays raw HTML or executes JavaScript when viewed in the admin area.

A user is affected if the Booking Manager plugin is installed with any user registration or booking form access enabled, and the database contains or admin pages display unsanitized user-submitted content.

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 the latest version of Booking Manager if a patch is available. Otherwise, implement proper input validation and output encoding on all booking form fields, particularly those that accept user-provided data and are displayed back in the admin dashboard or booking confirmation pages.

Have this fixed Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing3.0 h
  • Review / QA2.0 h
14.0 hours of engineering $2,490
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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