dbcve.org
Booking CalendarWordPress extension · Wpbookingcalendar

CVE-2023-51520

MEDIUM · 5.4 CVSS v3.1 Published 2024-02-01
Fix available
A fix is available. Upgrade to 9.7.4 or later.
See remediation →
58/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 / Oplugins WP Booking Calendar allows Stored XSS.This issue affects WP Booking Calendar: from n/a before 9.7.4.

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 · moderate confidence

A Stored Cross-Site Scripting (XSS) vulnerability exists in WP Booking Calendar plugin for WordPress before version 9.7.4. The vulnerability allows an attacker to inject malicious JavaScript code through input fields that are not properly sanitized, which then gets stored and executed when other users view the affected pages.

MitigationUpdate WP Booking Calendar to version 9.7.4 or later to remediate this vulnerability. As a secondary measure, implement Content Security Policy (CSP) headers to mitigate XSS execution.

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

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
Booking CalendarWordPress extension
Affected:< 9.7.4

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
None

CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:C/C:L/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 WP Booking Calendar plugin version
    Log in to WordPress admin, go to Plugins > Installed Plugins, find WP Booking Calendar and note the version number displayed. Alternatively, inspect the plugin main file header at wp-content/plugins/wpbookingcalendar/wpbookingcalendar.php for the 'Version' comment, or run: wp plugin list | grep wpbookingcalendar
    Affected if The displayed version is lower than 9.7.4 (e.g., 9.7.3, 9.6.0, etc.) or no version is shown (indicating an outdated release)
  2. Confirm plugin is active
    In WordPress admin under Plugins > Installed Plugins, verify that WP Booking Calendar shows as 'Active' rather than 'Inactive'
    Affected if The plugin is active and handling booking form submissions from users
  3. Identify active booking forms
    Go to Booking Calendar > Calendars or the bookings section in the admin panel to see if any booking forms are published and accepting submissions. Check your site pages for embedded booking form shortcodes like [bookingcalendar] or similar
    Affected if Booking forms exist and are accessible to site visitors, allowing them to submit data that gets stored
  4. Review recent booking submissions for suspicious content
    Access the booking submissions/received bookings in the WordPress admin panel (usually under Booking Calendar > Bookings or a similar menu item). Inspect input fields for unusual characters, script tags, or encoded content that may indicate XSS payloads
    Affected if Any booking submissions contain unsanitized user input that could include script tags or HTML elements

You are affected if the installed WP Booking Calendar version is below 9.7.4 AND the plugin is active with booking forms accepting user submissions, as this creates the conditions for stored XSS to execute when admin or other users view the submitted data.

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
Upgrade available Upgrade to 9.7.4 or later
Fixed in 9.7.4
Interim mitigation

Update WP Booking Calendar to version 9.7.4 or later to remediate this vulnerability. As a secondary measure, implement Content Security Policy (CSP) headers to mitigate XSS execution.

Recommended fix High confidence

9.7.4 or later

  1. Backup your WordPress site before performing any updates
  2. Log in to the WordPress admin dashboard
  3. Navigate to the Plugins menu
  4. Locate the 'Booking Calendar' plugin in the installed plugins list
  5. Check if an update is available for the plugin
  6. If an update is available, click 'Update Now' to install version 9.7.4 or later
  7. Alternatively, navigate to Dashboard > Updates and select Booking Calendar to update
  8. After updating, verify the plugin version shows 9.7.4 or higher in the Plugins list

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

Fix this in Booking Calendar Scoped from the published advisory
  • Consultation1.0 h
  • Implementation1.0 h
  • Testing2.0 h
  • Review / QA1.0 h
5.0 hours of engineering $860
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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