dbcve.org
Ba Book EverythingWordPress extension · Ba Booking

CVE-2024-32598

MEDIUM · 5.4 CVSS v3.1 Published 2024-04-18
Fix available
A fix is available. Upgrade to 1.6.9 or later.
See remediation →
58/100
Remediation priority · Elevated
Remotely reachable

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
Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting') vulnerability in Booking Algorithms BA Book Everything allows Stored XSS.This issue affects BA Book Everything: from n/a through 1.6.8.

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 confidence

Stored Cross-site Scripting (XSS) vulnerability in the BA Book Everything WordPress plugin allows authenticated attackers to inject malicious JavaScript code through input fields that are not properly sanitized. The malicious payload is stored in the database and executed when other users view booking-related pages, potentially leading to session hijacking or credential theft.

MitigationUpdate to the latest version of BA Book Everything plugin which includes proper input sanitization and output encoding. Until a patch is available, implement Web Application Firewall (WAF) rules to block XSS attack patterns and review all user input fields in the plugin for manual sanitization using WordPress escaping functions.

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
Affected:< 1.6.9

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

CVSS:3.1/AV:N/AC:L/PR:L/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. Locate BA Book Everything plugin version
    Navigate to WordPress admin dashboard > Plugins > Installed Plugins, find 'BA Book Everything' and check the version number displayed. Alternatively, inspect the plugin main file header in wp-content/plugins/ba-book-everything/ or check the plugin's readme.txt for the Version field.
    Affected if The installed version is lower than 1.6.9 (for example, 1.6.8, 1.6.7, etc.)
  2. Identify active booking form inputs
    In the WordPress admin, go to the BA Book Everything settings or booking form configuration pages. Identify all input fields used for collecting user data such as name, email, phone, address, or custom fields.
    Affected if The plugin is active and contains input fields that accept user-supplied data without visible sanitization indicators
  3. Inspect stored booking data for script tags
    Access the WordPress database (via phpMyAdmin or wp-cli) and query the plugin's booking data tables for any records containing HTML script tags or javascript: protocols. Run a query like: SELECT * FROM wp_babe_bookings WHERE booking_data LIKE '%<script%' OR booking_data LIKE '%javascript:%' (adjust table prefix if different).
    Affected if Any database records contain unsanitized script tags or event handler attributes (onerror, onload, etc.)
  4. Review booking-related page source
    View the source code of published booking pages on the frontend (pages containing booking forms or booking confirmation views). Search for unescaped user input being reflected in HTML attributes or content.
    Affected if User-supplied data from bookings appears in the page source without proper HTML encoding (visible as literal <script> tags or unescaped quotes in attributes)

A user is affected if the BA Book Everything plugin version is installed and is lower than 1.6.9, and either suspicious script tags exist in the booking database records or unescaped user input is visible in frontend booking pages.

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.

dbcve · scoped
Upgrade available Upgrade to 1.6.9 or later
Fixed in 1.6.9
Interim mitigation

Update to the latest version of BA Book Everything plugin which includes proper input sanitization and output encoding. Until a patch is available, implement Web Application Firewall (WAF) rules to block XSS attack patterns and review all user input fields in the plugin for manual sanitization using WordPress escaping functions.

Recommended fix High confidence

1.6.9

  1. 1. Back up your WordPress database and files before performing any updates
  2. 2. Navigate to the WordPress admin dashboard
  3. 3. Go to Plugins > Installed Plugins
  4. 4. Find 'BA Book Everything' in the plugin list
  5. 5. If an update is available, click 'Update Now' to upgrade to version 1.6.9
  6. 6. Alternatively, download version 1.6.9 from the official WordPress repository or the vendor
  7. 7. Deactivate and delete the current version, then upload and install version 1.6.9
  8. 8. Reactivate the plugin after installation
Caveat Review plugin changelog for any breaking changes between your current version and 1.6.9 before upgrading

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Ba Book Everything Scoped from the published advisory
  • Consultation4.0 h
  • Implementation12.0 h
  • Testing6.0 h
  • Review / QA3.0 h
25.0 hours of engineering $4,400
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $7,040.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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