dbcve.org
Booking CalendarWordPress extension · Booking Calendar Project

CVE-2023-36384

MEDIUM · 6.1 CVSS v3.1 Published 2023-07-18
Fix available
A fix is available. Upgrade to after 1.2.40 or later.
See remediation →
68/100
Remediation priority · Elevated
Remotely reachable No privileges

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
Unauth. Reflected Cross-Site Scripting (XSS) vulnerability in CodePeople Booking Calendar Contact Form plugin <= 1.2.40 versions.

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

Reflected Cross-Site Scripting (XSS) vulnerability in the CodePeople Booking Calendar Contact Form WordPress plugin allows unauthenticated attackers to inject malicious JavaScript through unsanitized input parameters. The vulnerability affects versions 1.2.40 and below.

MitigationUpdate the plugin to a version newer than 1.2.40. If no patched version is available, disable the plugin until a fix is released.

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:<= 1.2.40

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

CVSS:3.1/AV:N/AC:L/PR:N/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. Verify Booking Calendar plugin is installed
    In WordPress admin, go to Plugins > Installed Plugins and look for 'Booking Calendar Contact Form' or check the /wp-content/plugins/ directory for the booking-calendar folder
    Affected if The plugin is present in the WordPress installation
  2. Check installed plugin version
    In WordPress admin, go to Plugins > Installed Plugins, find Booking Calendar Contact Form, and view the version number displayed below the plugin name. Alternatively, check the version in the plugin's main PHP file header
    Affected if Version is 1.2.40 or lower
  3. Confirm plugin is active
    In WordPress admin, go to Plugins > Installed Plugins and verify the Booking Calendar plugin shows 'Active' status
    Affected if Plugin is active and handling HTTP requests
  4. Identify exposed booking form endpoints
    Check the site for pages containing the booking calendar shortcode (typically [CP_BOOKING_CALENDAR] or similar). These forms accept user input and are accessible to unauthenticated visitors
    Affected if Public-facing booking forms are present that accept user-submitted data

User is affected if the Booking Calendar Contact Form plugin version is 1.2.40 or lower and the plugin is active with public booking forms handling user input.

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
Upgrade available Upgrade to a release after 1.2.40
Interim mitigation

Update the plugin to a version newer than 1.2.40. If no patched version is available, disable the plugin until a fix is released.

Fix this in Booking Calendar Scoped from the published advisory
  • Consultation1.0 h
  • Implementation2.0 h
  • Testing1.0 h
  • Review / QA1.0 h
5.0 hours of engineering $890
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,424.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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