Booking Ultra Pro Appointments Booking CalendarWordPress extension · Bookingultrapro
CVE-2023-32511
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 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 · high confidenceUnauthenticated reflected cross-site scripting (XSS) vulnerability in the Booking Ultra Pro WordPress plugin versions 1.1.8 and below. Attackers can inject malicious JavaScript through unsanitized user input that is reflected back in HTTP responses without proper output encoding.
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 Ultra Pro 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.
-
Confirm Booking Ultra Pro plugin is installedNavigate to WordPress Admin > Plugins and look for 'Booking Ultra Pro Appointments Booking Calendar' in the installed plugins list, or check the /wp-content/plugins/booking-ultra-pro directory exists on the serverAffected if The plugin directory 'booking-ultra-pro' exists on the server or the plugin appears in the WordPress plugins list
-
Identify the installed plugin versionIn WordPress Admin > Plugins > Booking Ultra Pro, read the version number displayed below the plugin name. Alternatively, inspect the main plugin PHP file (usually bookingultra-pro.php) and look for the 'Version' header comment in the plugin file headerAffected if The version displayed is 1.1.8 or lower, or the Version header shows a number <= 1.1.8
-
Verify if unauthenticated access is possibleConfirm the plugin endpoints are accessible without authentication by testing public booking pages or forms created with the plugin, without logging into WordPressAffected if The booking functionality is accessible to unauthenticated visitors (guest users)
-
Check for reflected parameters in plugin requestsSubmit a test request to a plugin endpoint (such as a booking form or search function) with a test parameter value like '<script>alert(1)</script>' and inspect the HTTP response to see if the value is reflected without encodingAffected if The test payload appears unencoded in the HTTP response (the browser would execute the script if the response were rendered)
A user is affected if the Booking Ultra Pro plugin version is 1.1.8 or lower AND the plugin is active with publicly accessible booking functionality that reflects user input without encoding.
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 Booking Ultra Pro Appointments Booking Calendar Plugin to a version newer than 1.1.8, or implement proper input validation and output encoding on all user-supplied parameters in the plugin code.
Fix this in Booking Ultra Pro Appointments Booking Calendar
Scoped from the published advisory
- Consultation3.0 h
- Implementation6.0 h
- Testing3.0 h
- Review / QA2.0 h
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 locallyCheck whether your project pulls in CVE-2023-32511 — 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-32511 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