SVG Support <= 2.5.7 - Authenticated (Author+) Cross-Site Scripting via SVG
Strategic Overview
- Status
- Patched in 2.5.8
- Affected Plugin
- SVG Support
- Affected Version
<= 2.5.7- CVSS
- 5.4Medium
- Weakness type
- CWE-79 · Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting')
- CVE
CVE-2023-6708
At a glance
CVE-2023-6708 is a medium-severity Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting') vulnerability in the SVG Support WordPress plugin, affecting versions <= 2.5.7. It carries a CVSS score of 5.4 (reachable over the network; low attack complexity). Exploitation requires an authenticated account at Author level or above. The issue is fixed in version 2.5.8; sites on affected versions should update now. Disclosed July 2024, reported by Nathanial Lattimer (d0nut).
Vulnerability Overview
The SVG Support plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the SVG upload feature in all versions up to, and including, 2.5.7 due to insufficient input sanitization and output escaping, even when the 'Sanitize SVG while uploading' feature is enabled. 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 an injected page. Note that successful exploitation of this vulnerability requires the administrator to allow author-level users to upload SVG files. As of 2.5.6, SVG sanitization can still be bypassed by supplying a content-type other than image/svg+xml.
Technical Analysis
The vector marks this flaw as remotely reachable over the network, with low attack complexity — no special timing or configuration is needed.
CWE-79: Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting')
Reaching this weakness in SVG Support <= 2.5.7 takes an account at Author level or above. Cross-site scripting happens when input from a request is written into a page without being escaped for the context it lands in, so the browser parses attacker-supplied text as markup or script.
Injected script runs with the privileges of whoever views the affected page, which is how these flaws turn into administrator session theft, silent account creation or persistent backdoors in page content. For SVG Support the fix is 2.5.8: builds <= 2.5.7 are affected, anything from 2.5.8 onward is not.
Remediation
Update to version 2.5.8, or a newer patched version
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. None of that substitutes for the fix: SVG Support 2.5.8 closes this, and updating the plugin is the step that ends it.
- Firewall
- Alerts
External References
Related records
Same weakness class
- 6.4CVE-2026-13340: SVG Support <= 2.5.16 Stored Cross-Site Scripting
CVE-2026-13340 - 6.4CVE-2024-10222: SVG Support <= 2.5.10 Stored Cross-Site Scripting
CVE-2024-10222 - 6.4CVE-2022-4022: SVG Support 2.5 - 2.5.1 Insecure Plugin Defaults to XSS
CVE-2022-4022 - 6.4CVE-2022-1755: SVG Support <= 2.4.2 Stored Cross-Site Scripting
CVE-2022-1755
Vulnerability data © Defiant, Inc., provided under the Wordfence Intelligence T&C