CVE-2026-13340

SVG Support < 2.5.17 - Author+ Stored XSS via .svgz Sanitization Bypass

Published Aug 3, 2026 CVSS 3.1 · 6.1 Medium EPSS < 1% KEV · Not listed
Description
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.

Analysis

AI-generated

Technical impact

The SVG Support plugin fails to apply sanitization to files with a .svgz extension. A user who can upload SVGs, such as an author with upload permissions, can place a script‑laden .svgz file. Because the plugin serves the file as SVG, the embedded script executes in any browser that loads the image, providing a stored XSS vector that can compromise account data and allow further payload delivery.

Affected Systems

WordPress sites running the SVG Support plugin in any version earlier than 2.5.17 are affected. The plugin is identified as "SVG Support" and is available to all WordPress installations that have installed it.

Risk and Exploitability

The vulnerability has a CVSS score of 6.1, indicating medium severity. The EPSS score is < 1% and it is not listed in the CISA KEV catalog. Attackers must first obtain upload privileges (e.g., via the Author role or an attacker who has gained that capability). Once a malicious .svgz file is uploaded, the site serves the file as SVG and any visitor who opens the file, including administrators, will have the injected JavaScript executed in their browser, enabling session hijacking, defacement, or further exploitation.

Remediation

No solution or workaround provided in the CVE record.

OpenCVE Recommended Actions

  • Upgrade the SVG Support plugin to version 2.5.17 or later.
  • If an upgrade is not immediately possible, configure the WordPress upload settings or use a security plugin to block .svgz file uploads entirely.
  • Verify that the user roles on the site are restricted and that authors or other less‑privileged users do not have permission to upload SVG files unless absolutely necessary.
  • Monitor site activity for anomalous uploads and report suspicious files to the plugin maintainers.

Generated by OpenCVE AI on August 4, 2026 at 10:40 UTC.

Tracking

Sign in to view the affected projects.

Advisories

No advisories available
History
Type Values Removed Values Added
First Time appeared Wordpress-extensions
Wordpress-extensions svg Support
Vendors & Products Wordpress-extensions
Wordpress-extensions svg Support
Type Values Removed Values Added
Metrics cvssV3_1

{'score': 6.1, 'vector': 'CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N'}

ssvc

{'options': {'Automatable': 'no', 'Exploitation': 'poc', 'Technical Impact': 'partial'}, 'version': '2.0.3'}

Type Values Removed Values Added
Weaknesses CWE-79
Type Values Removed Values Added
Description 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.
Title SVG Support < 2.5.17 - Author+ Stored XSS via .svgz Sanitization Bypass
References
Weaknesses
  • CWE-79

    Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting')

Sources

Status
PUBLISHED
Assigner
WPScan
Published
Updated
Aug 3, 2026, 5:04 PM
Reserved
Jun 25, 2026, 2:09 PM
Status
Deferred
Published
Aug 3, 2026, 7:16 AM
Modified
Aug 26, 2026, 4:31 PM