SVGMagic <= 1.1 - Authenticated (Author+) Stored Cross-Site Scripting via SVG Upload
Strategic Overview
- Status
- Unpatched
- Affected Plugin
- SVGMagic
- Affected Version
<= 1.1- CVSS
- 6.4Medium
- Weakness type
- CWE-434 · Unrestricted Upload of File with Dangerous Type
- CVE
CVE-2024-4270
At a glance
CVE-2024-4270 is a medium-severity Unrestricted Upload of File with Dangerous Type vulnerability in the SVGMagic WordPress plugin, affecting versions <= 1.1. It carries a CVSS score of 6.4 (reachable over the network; low attack complexity). Exploitation requires an authenticated account at Author level or above. No fixed release has been reported yet; treat installations running this software as exposed. Disclosed May 2024, reported by Rayhan Ramdhany Hanaputra.
Vulnerability Overview
The SVGMagic plugin for WordPress is vulnerable to Stored Cross-Site Scripting via SVG File uploads in all versions up to, and including, 1.1 due to insufficient input sanitization and output escaping. This makes it possible for authenticated attackers, with Author-level access and above, 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 interaction from a victim user.
CWE-434: Unrestricted Upload of File with Dangerous Type
Reaching this weakness in SVGMagic <= 1.1 takes an account at Author level or above. 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. No fixed build of this plugin is recorded for SVGMagic yet, so installs running <= 1.1 stay exposed until the vendor ships one.
Remediation
No known patch available. Please review the vulnerability's details in depth and employ mitigations based on your organization's risk tolerance. It may be best to uninstall the affected software and find a replacement.
How does WordSec protect against this?
An attacker needs Author access first, so the firewall sees the attempt as traffic from a logged-in account: 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. No patched version is recorded yet, which is the case where a filtering layer matters most, because there is nothing to update to.
- Firewall
- Scanner
- Alerts
External References
Vulnerability data © Defiant, Inc., provided under the Wordfence Intelligence T&C