dbcve.org
Unrestricted File UploadWeakness · CWE-434

CVE-2024-9504

HIGH · 7.2 CVSS v3.1 Published 2024-11-26
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
81/100
Remediation priority · High
Remotely reachable No privileges Zero-click

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
The Booking calendar, Appointment Booking System plugin for WordPress is vulnerable to Stored Cross-Site Scripting via SVG File uploads in all versions up to, and including, 3.2.15 due to insufficient input sanitization and output escaping. This makes it possible for unauthenticated attackers to inject arbitrary web scripts in pages that will execute whenever a user accesses the SVG file.

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 confidence

The Booking Calendar plugin for WordPress versions up to 3.2.15 allows unauthenticated attackers to upload SVG files containing malicious JavaScript. Due to insufficient input sanitization of SVG content and improper output escaping, injected scripts persist and execute when users access these uploaded SVG files, resulting in stored XSS.

MitigationUpdate the plugin to version 3.2.16 or later. Until patched, consider disabling SVG uploads at the server level (e.g., via .htaccess or web server config) or implementing strict Content-Security-Policy headers.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

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

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/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. Confirm Booking Calendar plugin is installed
    In WordPress admin, go to Plugins > Installed Plugins and look for 'Booking Calendar' or check the plugin files in wp-content/plugins/booking-calendar/ for a version file
    Affected if The plugin is present in the installation
  2. Determine installed plugin version
    Check the plugin main file header or version file within wp-content/plugins/booking-calendar/ for the version number
    Affected if Version is 3.2.15 or earlier (the vulnerability affects versions up to 3.2.15)
  3. Verify SVG upload capability is enabled
    Inspect WordPress media settings or plugin settings to confirm SVG files can be uploaded; check if the plugin accepts file uploads in any frontend booking forms
    Affected if SVG uploads are allowed and the booking form accepts file attachments
  4. Scan uploaded SVG files for script content
    Examine SVG files in wp-content/uploads/ directories for <script> tags, javascript: URIs, or event handler attributes (onclick, onerror, etc.)
    Affected if Any SVG files contain embedded JavaScript or event handlers

You are affected if the Booking Calendar plugin version is 3.2.15 or earlier AND SVG file uploads are enabled, particularly if untrusted users can submit files through booking forms.

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
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Update the plugin to version 3.2.16 or later. Until patched, consider disabling SVG uploads at the server level (e.g., via .htaccess or web server config) or implementing strict Content-Security-Policy headers.

Recommended fix Moderate confidence

Latest version higher than 3.2.16 (check WordPress plugin repository for current release)

  1. Log in to WordPress admin dashboard
  2. Navigate to Plugins > Installed Plugins
  3. Locate the 'Booking calendar, Appointment Booking System' plugin
  4. Check if an update is available (version should be higher than 3.2.15)
  5. If update available, click 'Update Now' to install the latest version
  6. After updating, verify the plugin is working correctly
  7. Consider restricting SVG file uploads at the server level as an additional defense-in-depth measure using .htaccess or server configuration
Caveat Review plugin changelog for any breaking changes between your current version and the new version before updating

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

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing4.0 h
  • Review / QA2.0 h
12.0 hours of engineering $2,080
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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