Appointments Booking CalendarWordPress extension · Bookingultrapro
CVE-2023-32236
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 · uneditedUnauth. Reflected Cross-Site Scripting (XSS) vulnerability in Booking Ultra Pro Booking Ultra Pro Appointments Booking Calendar Plugin <= 1.1.8 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 · moderate confidenceAn unauthenticated reflected cross-site scripting (XSS) vulnerability in the Booking Ultra Pro Appointments Booking Calendar Plugin versions 1.1.8 and below allows attackers to inject malicious JavaScript through unsanitized user input that gets reflected back in the web application's HTTP response.
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
Appointments Booking CalendarWordPress extension
<= 1.1.8CVSS 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 checksWork through these to decide whether this CVE applies to you.
-
Check the installed plugin versionAccess the WordPress admin panel under Plugins > Installed Plugins and locate Booking Ultra Pro Appointments Booking Calendar to view the current version number, or inspect the main plugin PHP file header for the Version fieldAffected if The installed version is 1.1.8 or lower
-
Verify the plugin is active and publicly accessibleVisit the website frontend and navigate to any booking-related page or endpoint that loads the plugin functionality without requiring authenticationAffected if The plugin is active and its booking forms or endpoints are accessible to unauthenticated visitors
-
Identify reflected input parametersReview HTTP requests sent to the plugin endpoints (typically under /booking-ultrapro/ or similar URL paths) and identify parameters that accept user input and reflect it back in the server response without encodingAffected if Any user-supplied parameter value is returned verbatim in the HTML response without sanitization
-
Confirm XSS vulnerability existsSubmit a test payload such as <script>alert(1)</script> in the identified reflected parameter and examine whether the payload appears unescaped in the resulting HTML pageAffected if The payload is reflected in the response without HTML encoding and would execute if viewed in a browser
If the plugin version is 1.1.8 or lower and unauthenticated users can access booking functionality where user input is reflected without sanitization, the environment is affected by this CVE.
Generated from the published advisory. Verify against your own configuration.
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 dataUpdate the plugin to a version newer than 1.1.8 that includes proper input validation and output encoding, or implement WAF rules to filter malicious XSS payloads until the patch can be applied.
Fix this in Appointments Booking Calendar
Scoped from the published advisory
- Consultation2.0 h
- Implementation4.0 h
- Testing3.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,800.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2023-32236 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2023-32236 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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