Booking Ultra Pro Appointments Booking CalendarWordPress extension · Bookingultrapro
CVE-2021-36855
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 · uneditedCross-Site Scripting (XSS) via Cross-Site Request Forgery (CSRF) vulnerability in Booking Ultra Pro plugin <= 1.1.4 at WordPress.
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 confidenceA stored Cross-Site Scripting (XSS) vulnerability in the Booking Ultra Pro WordPress plugin (version 1.1.4 and below) allows attackers to inject malicious JavaScript through forms that lack proper CSRF protection, enabling script execution when administrators view the injected content.
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.4CVSS 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 installed Booking Ultra Pro versionIn WordPress admin, go to Plugins > Installed Plugins > Booking Ultra Pro and view the version number. Alternatively, check the plugin header in /wp-content/plugins/booking-ultra-pro/booking-ultra-pro.php for the Version field.Affected if Version displayed is 1.1.4 or lower
-
Verify plugin is activeConfirm the Booking Ultra Pro plugin is currently activated in the WordPress site. Check Plugins > Installed Plugins for an active status.Affected if Plugin shows as Active and version is <= 1.1.4
-
Inspect booking forms for CSRF protectionView the HTML source of any Booking Ultra Pro frontend form (appointment booking form, contact form, etc.) and examine the form tags for the presence of a CSRF token field (look for fields like nonce, token, csrf, or wp_nonce).Affected if No CSRF token field is found in the form markup and plugin version is <= 1.1.4
-
Check WordPress posts/database for injected contentIn WordPress admin, navigate to the booking management section or view recent bookings/appointments. Manually inspect any custom fields, notes, or user-submitted content for suspicious script tags, iframe tags, or JavaScript: URLs.Affected if Any booking records contain unsanitized HTML/script tags that could execute XSS when viewed by an administrator
A user is affected if the Booking Ultra Pro plugin version is 1.1.4 or lower, the plugin is active, and booking forms accept user input without CSRF protection or display unsanitized content to administrators.
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 Booking Ultra Pro to the latest version beyond 1.1.4, or implement anti-CSRF tokens in all plugin forms and apply proper input sanitization and output encoding to prevent XSS.
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-2021-36855 — 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-2021-36855 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