CVE-2024-9504

Booking calendar, Appointment Booking System <= 3.2.15 - Unauthenticated Stored Cross-Site Scripting via SVG File Upload

2024-11-25 00:00
Rein Daelman (trein)

Strategic Overview

Status
Patched in 3.2.16
Affected Version
<= 3.2.15
CVSS
7.2High
Weakness type
CWE-434 · Unrestricted Upload of File with Dangerous Type
CVE
CVE-2024-9504
View all Booking calendar, Appointment Booking System vulnerabilities

At a glance

CVE-2024-9504 is a high-severity Unrestricted Upload of File with Dangerous Type vulnerability in the Booking calendar, Appointment Booking System WordPress plugin, affecting versions <= 3.2.15. It carries a CVSS score of 7.2 (reachable over the network; low attack complexity). Exploitation requires no authentication. The issue is fixed in version 3.2.16; sites on affected versions should update now. Disclosed November 2024, reported by Rein Daelman (trein).

Vulnerability Overview

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 Analysis

The vector marks this flaw as remotely reachable over the network, with low attack complexity — no special timing or configuration is needed, and no privileges on the target site, and no interaction from a victim user.

CWE-434: Unrestricted Upload of File with Dangerous Type

Reaching this weakness in Booking calendar, Appointment Booking System <= 3.2.15 takes no account at all. An unrestricted file upload lets a caller store a file whose type or destination the application does not properly constrain.

If an uploaded file lands anywhere the server will execute, the flaw becomes remote code execution and the site should be treated as fully compromised. For Booking calendar, Appointment Booking System the fix is 3.2.16: builds <= 3.2.15 are affected, anything from 3.2.16 onward is not.

Remediation

Update to version 3.2.16, or a newer patched version

How does WordSec protect against this?

Requests carrying this pattern arrive without a session, so nothing upstream of the firewall gets a chance to reject them: WordSec's web application firewall inspects request payloads before WordPress loads them. Classes like this one can leave something behind, so the staged malware scanner is the second half: it looks for dropped files and modified code rather than for the request that created them. None of that substitutes for the fix: Booking calendar, Appointment Booking System 3.2.16 closes this, and updating the plugin is the step that ends it.

  • Firewall
  • Scanner
  • Login Security

External References

Related records

Vulnerability data © Defiant, Inc., provided under the Wordfence Intelligence T&C