WordPress plugin · Updated daily · Source: Wordfence Intelligence

SVG Support vulnerabilities: affected versions and fixes

SVG Support has 1+ million active installs. Here are its publicly disclosed vulnerabilities, whether your version is affected, and what to do now.

SVG Support at a glance

  • 8 publicly disclosed vulnerabilities. The most recent was disclosed on Jul 24, 2026.
  • Ranked #48 by popularity on WordPress.org (1+ million active installs).
  • The latest version is 2.6.4 (released Nov 14, 2026). The most recent security fix shipped in 2.5.17.
  • Every disclosed vulnerability has a fix. If you are on the latest version, none of them apply to you.
  • The first thing to do: update to the latest version and turn on automatic updates.

Check your SVG Support version

Enter the SVG Support version number shown on your Plugins screen to see only the vulnerabilities that apply to it, most serious first.

Your version number is compared on this page only. It is not sent anywhere.

Get an email when a new vulnerability is disclosed

We'll tell you when a new vulnerability is disclosed in “SVG Support”, with the version that fixes it. Free, email address only, stop any time.

We use your email address only for these alerts. Privacy policy

Want every plugin and theme on your site checked daily?

With Security Ready Standard, just install the “KazLinks Security Ready” plugin from WordPress.org. It sends only the names and versions of your plugins and themes, and we check them against disclosed vulnerabilities every day. Your first in-depth scan is free.

View the plugin on wordpress.orgGet a free in-depth scan

How to check whether your site is affected

  1. 1

    Find your version

    In your WordPress dashboard, open Plugins → Installed Plugins and look at the version number under “SVG Support”.

  2. 2

    Compare it with the list below

    If your version falls within “Affected versions”, that vulnerability applies to you. If you are on the “Fixed in” version or later, it does not.

  3. 3

    Update

    Click “Update now” to move to the latest version (2.6.4). Taking a backup first is a good idea.

  4. 4

    Turn on automatic updates

    On the same screen, click “Enable auto-updates” so future fixes are installed automatically.

Known SVG Support vulnerabilities

  • SVG Support <= 2.5.16 - Authenticated (Author+) Stored Cross-Site Scripting

    Cross-site scripting (XSS) · CVE-2026-13340

    Affected versions: ≤ 2.5.16

    Fixed in: 2.5.17

    Severity: Medium 6.4 · Disclosed Jul 24, 2026

  • SVG Support <= 2.5.14 - Missing Authorization

    Missing authorization · CVE-2026-48973

    Affected versions: ≤ 2.5.14

    Fixed in: 2.5.15

    Severity: Medium 4.3 · Disclosed May 27, 2026

  • SVG Support <= 2.5.8 - Stored Cross-Site Scripting via Vulnerability Dependency

    Cross-site scripting (XSS) · CVE-2022-23638

    Affected versions: ≤ 2.5.8

    Fixed in: 2.5.9

    Severity: Medium 5.4 · Disclosed Feb 24, 2025

  • SVG Support <= 2.5.10 - Authenticated (Author+) Stored Cross-Site Scripting via SVG File Upload

    Cross-site scripting (XSS) · CVE-2024-10222

    Affected versions: ≤ 2.5.10

    Fixed in: 2.5.11

    Severity: Medium 6.4 · Disclosed Feb 21, 2025

  • SVG Support <= 2.5.7 - Authenticated (Author+) Cross-Site Scripting via SVG

    Cross-site scripting (XSS) · CVE-2023-6708

    Affected versions: ≤ 2.5.7

    Fixed in: 2.5.8

    Severity: Medium 5.4 · Disclosed Jul 17, 2024

  • SVG Support 2.5 - 2.5.1 - Insecure Plugin Defaults to Cross-Site Scripting

    Cross-site scripting (XSS) · CVE-2022-4022

    Affected versions: ≥ 2.5, ≤ 2.5.1

    Fixed in: 2.5.2

    Severity: Medium 6.4 · Disclosed Nov 16, 2022

  • SVG Support <= 2.4.2 - Authenticated (Author+) Stored Cross-Site Scripting

    Cross-site scripting (XSS) · CVE-2022-1755

    Affected versions: ≤ 2.4.2

    Fixed in: 2.5

    Severity: Medium 6.4 · Disclosed Sep 5, 2022

  • SVG Support <= 2.3.19 Admin+ Cross-Site Scripting

    Cross-site scripting (XSS) · CVE-2021-24686

    Affected versions: ≤ 2.3.19

    Fixed in: 2.3.20

    Severity: Medium 5.5 · Disclosed Jan 3, 2022

Vulnerability data: Wordfence Intelligence (Copyright Defiant, Inc. · license terms). Severity is the CVSS score (0–10). Most recent disclosure: Jul 24, 2026.

Most common weaknesses in SVG Support

Cross-site scripting (XSS)

7 issues

An attacker plants a malicious script on a page so that it runs in visitors’ browsers. If an administrator opens that page, the attacker can steal their session or act as the administrator.

Missing authorization

1 issue

Actions that should require a login or a particular role can be carried out without the proper check. Attackers use this to change settings or read data they should not see.

Frequently asked questions

Is SVG Support safe to use?

SVG Support is a well-known plugin with 1+ million active installs. Finding vulnerabilities in popular plugins is common, and most of them are fixed in newer versions. The important thing is to stay on the latest version (2.6.4) and turn on automatic updates.

How do I find which version of SVG Support my site is running?

In your WordPress dashboard, go to Plugins → Installed Plugins. The version number is shown under the plugin name. If you see “There is a new version available”, you are on an older version.

Could updating break my site?

Occasionally an update changes how something looks or works, so take a backup before updating. If an agency or developer maintains your site, send them a link to this page and ask them to update.

Can I check all my other plugins too?

Yes. Security Ready reads the versions of every plugin and theme on your site, matches them against known vulnerabilities every day, and tells you what to fix. Your first in-depth scan is free.

Check every plugin and theme automatically, every day

Security Ready reads the versions of every plugin, theme and WordPress core on your site, matches them against known vulnerabilities every day, and tells you how to fix what it finds. Your first in-depth scan is free, and no payment details are needed.

Think your site has already been hacked? Before updating, read what to do in the first hour. Updating alone does not remove a backdoor that has already been planted.

← All plugin vulnerabilitiesSVG Support on WordPress.org