HomeWordPress vulnerabilitiesSVG Support
SVG Support vulnerabilities
SVG Support has 6 known vulnerabilities in this database. The most recent published record is dated 3 Aug 2026.
- Known vulnerabilities
- 6
- Active installs
- 1m+
- Latest version
- 2.6.1
- Last updated
- 25 Jul 2026
- Most recent
- 3 Aug 2026
Find it in your WordPress dashboard under Plugins. Severity is based on the CVSS score published with the CVE where one is available.
| Vulnerability | Severity | Affected | Fix | Published |
|---|---|---|---|---|
| Cross-site scripting (XSS) CVE-2026-13340 | Medium 6.1 | Before 2.5.17 | Fixed in 2.5.17 | 3 Aug 2026 |
| Cross-site scripting (XSS) CVE-2024-10222 | Medium 6.4 | Before 2.5.11 | Fixed in 2.5.11 | 21 Feb 2025 |
| Cross-site scripting (XSS) CVE-2023-6708 | Medium 5.4 | Up to 2.5.7 | Fixed in a later version (latest 2.6.1) | 18 Jul 2024 |
| Cross-site scripting (XSS) CVE-2022-4022 | Medium 6.4 | Before 2.5.2 | Fixed in 2.5.2 | 16 Nov 2022 |
| Cross-site scripting (XSS) CVE-2022-1755 | Medium 5.4 | Before 2.5.0 | Fixed in 2.5.0 | 26 Sep 2022 |
| Cross-site scripting (XSS) CVE-2021-24686 | Medium 4.8 | Before 2.3.20 | Fixed in 2.3.20 | 1 Feb 2022 |
Read the published descriptions
- CVE-2026-13340, 3 Aug 2026
- The SVG Support WordPress plugin before 2.5.17 does not apply its SVG sanitisation to uploaded files using the .svgz extension, even though it registers and serves them as SVG, allowing a user permitted to upload SVGs (such as an Author once granted upload access) to store a script-bearing file that executes in the browser of anyone who later views it, including an administrator. CVE record
- CVE-2024-10222, 21 Feb 2025
- The SVG Support plugin for WordPress is vulnerable to Stored Cross-Site Scripting via SVG File uploads in all versions up to, and including, 2.5.10 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. By default, this can only be exploited by administrators, but the ability to upload SVG files can be extended to authors. CVE record
- CVE-2023-6708, 18 Jul 2024
- 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. CVE record
- CVE-2022-4022, 16 Nov 2022
- The SVG Support plugin for WordPress defaults to insecure settings in version 2.5 and 2.5.1. SVG files containing malicious javascript are not sanitized. While version 2.5 adds the ability to sanitize image as they are uploaded, the plugin defaults to disable sanitization and does not restrict SVG upload to only administrators. This allows authenticated attackers, with author-level privileges and higher, to upload malicious SVG files that can be embedded in posts and pages by higher privileged users. Additionally, the embedded JavaScript is also triggered on visiting the image URL, which allows an attacker to execute malicious code in browsers visiting that URL. CVE record
- CVE-2022-1755, 26 Sep 2022
- The SVG Support WordPress plugin before 2.5 does not properly handle SVG added via an URL, which could allow users with a role as low as author to perform Cross-Site Scripting attacks CVE record
- CVE-2021-24686, 1 Feb 2022
- The SVG Support WordPress plugin before 2.3.20 does not escape the "CSS Class to target" setting before outputting it in an attribute, which could allow high privilege users to perform Cross-Site Scripting attacks even when the unfiltered_html capability is disallowed. CVE record
What to do if you run SVG Support
If you run SVG Support, open WordPress and check the installed version in Plugins. Compare it with the affected versions in the vulnerability record. If a fixed version is available, take a current backup and update to that version or the latest supported release.
If no fixed version exists, consider disabling and removing the plugin or replacing it with a maintained alternative. After dealing with the affected software, check administrator users, unexpected file changes, redirects, unfamiliar pages and security logs for signs that the site may already have been altered.
Email me about new SVG Support vulnerabilities
Free. We email you when a new vulnerability is published for SVG Support, usually within minutes. Confirm by email; unsubscribe any time.
Focus on your business. We’ll take care of your website.
From everyday updates to ongoing care, we keep your website working.