SVG Support skips sanitization for compressed SVG uploads
SVG Support before 2.5.17 registers and serves .svgz files as SVG but does not pass them through its SVG sanitizer. A user permitted to upload SVG files, such as an Author after SVG upload access is granted, can upload a compressed script-bearing SVG that executes in the browser of visitors or Administrators who view it.
- Component
- SVG Support
- Plugin slug
svg-support- Affected
- < 2.5.17
- Safe version
2.5.17- Published
- Aug 03, 2026
This CVE was published Aug 03, 2026 and is one of 7 known issues for this plugin.
Update, patch or deactivate.
Update SVG Support to 2.5.17 or later. Review .svgz uploads by delegated authors, remove script-bearing files and invalidate privileged sessions if Administrators viewed suspicious uploads.
A safe version is available, so updating to that version or later is the preferred remediation. If an immediate update is not practical, consider a targeted application patch or temporarily restricting the affected functionality.
Deactivate only when warranted by your risk profile, or when advised by your hosting provider in the limited circumstances where the vulnerability cannot otherwise be mitigated. If you’re unsure which action is appropriate, contact Fused or your hosting provider for guidance.
Technical 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.
CVE / CNA vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N