Booster for WooCommerce 4.0.1 - 7.2.4 - Unauthenticated Stored Cross-Site Scripting
Strategic Overview
- Status
- Patched in 7.2.5
- Affected Plugin
- Booster for WooCommerce – PDF Invoices, Abandoned Cart, Variation Swatches & 100+ Tools
- Affected Version
4.0.1 – 7.2.4- CVSS
- 7.2High
- Weakness type
- CWE-434 · Unrestricted Upload of File with Dangerous Type
- CVE
CVE-2024-13708
At a glance
CVE-2024-13708 is a high-severity Unrestricted Upload of File with Dangerous Type vulnerability in the Booster for WooCommerce WordPress plugin, affecting versions 4.0.1 – 7.2.4. 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 7.2.5; sites on affected versions should update now. Disclosed April 2025, reported by lucky_buddy.
Vulnerability Overview
The Booster for WooCommerce plugin for WordPress is vulnerable to Stored Cross-Site Scripting via SVG File uploads in versions 4.0.1 to 7.2.4 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 Booster for WooCommerce 4.0.1 – 7.2.4 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 Booster for WooCommerce the fix is 7.2.5: builds 4.0.1 – 7.2.4 are affected, anything from 7.2.5 onward is not.
Remediation
Update to version 7.2.5, 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: Booster for WooCommerce 7.2.5 closes this, and updating the plugin is the step that ends it.
- Firewall
- Scanner
- Login Security
External References
Related records
Same weakness class
Other vulnerabilities in Booster for WooCommerce – PDF Invoices, Abandoned Cart, Variation Swatches & 100+ Tools
- 9.8CVE-2021-34646: Booster for WooCommerce <= 5.4.3 Authentication Bypass
CVE-2021-34646 - 8.8Booster for WooCommerce <= 5.6.8 Cross-Site Request Forgery
- 8.8CVE-2022-3763: Booster for WooCommerce… , Premium <= 5.6.4) - CSRF
CVE-2022-3763 - 8.8CVE-2022-41805: Booster for WooCommerce <= 5.6.6 CSRF
CVE-2022-41805 - 8.8Booster for WooCommerce <= 5.6.1 Cross-Site Request Forgery
- 7.2CVE-2024-12278: Booster for WooCommerce <= 7.2.4 Stored XSS
CVE-2024-12278 - 7.2Booster for WooCommerce 7.0.0 Arbitrary Options Update
- 6.5CVE-2024-3957: Booster for WooCommerce Arbitrary Shortcode Execution
CVE-2024-3957
Vulnerability data © Defiant, Inc., provided under the Wordfence Intelligence T&C