CVE-2026-13340

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

2026-07-24 00:00
Shivamani Vastrala

Strategic Overview

Status
Patched in 2.5.17
Affected Plugin
SVG Support
Affected Version
<= 2.5.16
CVSS
6.4Medium
Weakness type
CWE-79 · Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting')
CVE
CVE-2026-13340
View all SVG Support vulnerabilities

At a glance

CVE-2026-13340 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.16. 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. The issue is fixed in version 2.5.17; sites on affected versions should update now. Disclosed July 2026, reported by Shivamani Vastrala.

Vulnerability Overview

The SVG Support plugin for WordPress is vulnerable to Stored Cross-Site Scripting in versions up to, and including, 2.5.16 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 an injected page.

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-79: Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting')

Reaching this weakness in SVG Support <= 2.5.16 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.17: builds <= 2.5.16 are affected, anything from 2.5.17 onward is not.

Remediation

Update to version 2.5.17, 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.17 closes this, and updating the plugin is the step that ends it.

  • Firewall
  • Alerts

External References

https://www.cve.org/CVERecord?id=CVE-2026-13340https://www.wordfence.com/threat-intel/vulnerabilities/id/938852c9-bc9b-4215-9e6b-9af122d1e8e7https://nvd.nist.gov/vuln/detail/CVE-2026-13340

Related records

Vulnerability data © Defiant, Inc., provided under the Wordfence Intelligence T&C