Ba Book EverythingWordPress extension · Ba Booking
CVE-2024-47360
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 · uneditedImproper Neutralization of Input During Web Page Generation ('Cross-site Scripting') vulnerability in bookingalgorithms BA Book Everything ba-book-everything.This issue affects BA Book Everything: from n/a through <= 1.6.20.
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 confidenceStored XSS vulnerability in the BA Book Everything WordPress plugin allows attackers to inject malicious JavaScript through unsanitized input fields that are rendered in web pages 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
Ba Book EverythingWordPress extension
< 1.6.21CVSS 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 BA Book Everything plugin is installedLog into WordPress admin dashboard, navigate to Plugins > Installed Plugins, and look for 'BA Book Everything' or 'Ba Booking' in the list of active pluginsAffected if The plugin appears in the installed plugins list
-
Identify installed plugin versionIn WordPress admin, go to Plugins > Installed Plugins, find BA Book Everything, and note the version number displayed below the plugin nameAffected if Version number is lower than 1.6.21 (for example, 1.6.20, 1.5.0, etc.)
-
Verify plugin is activeIn Plugins > Installed Plugins, confirm the BA Book Everything plugin has the 'Active' status enabledAffected if Plugin is active and version is below 1.6.21
-
Check for user-facing input formsVisit pages on the site where booking forms, user input fields, or data submission forms provided by BA Book Everything are renderedAffected if Plugin is active, version is vulnerable, and input fields accepting user data are present and accessible
You are affected if BA Book Everything plugin is installed with a version number lower than 1.6.21 and the plugin's input forms are active and accessible on the website.
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.
dbcve · scoped1.6.21
Update BA Book Everything plugin to the latest patched version, or implement proper input sanitization and output encoding on all user-supplied data before rendering in HTML.
1.6.21
- 1. Backup your WordPress site and database before proceeding with any updates
- 2. Update the BA Book Everything plugin to version 1.6.21 or later
- 3. Verify the update was successful by checking the plugins page in WordPress admin
- 4. Test the booking functionality to ensure the plugin works correctly after the update
- 5. Clear any caching plugins or server-side caches to ensure the patched code is served
Generated from the published advisory — verify against the referenced sources before acting.
Fix this in Ba Book Everything
Scoped from the published advisory
- Consultation2.0 h
- Implementation2.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 $2,512.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-47360 — 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-2024-47360 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