WP-SVG

WP-SVG has one disclosed vulnerability in the WordSec catalog, all reported in 2024; it remains unpatched as of September 2026. Their average CVSS score is 6.4, and the most serious one scores 6.4 out of 10.

The most common weakness is Cross-Site Scripting, behind 1 of the records (100%).

The one issue recorded for WP-SVG has no published fix yet, which makes virtual patching the only reliable mitigation. The oldest unresolved one dates back to 2024.

All of these findings were reported by Bob Matyas. WP-SVG is installed on roughly 10 WordPress sites, so each unpatched flaw has a wide blast radius. The current release is tested up to WordPress 3.3.2.

Strategic Overview

Avg CVSSMedium

6.4/ 10

Patch Coverage0%

Open

Fixed

Get automatic notifications for all WP-SVG vulnerabilities before they are exploited.

Most severe open issueCVSS 6.4CVE-2024-11644

WP-SVG <= 0.9 - Authenticated (Contributor+) Stored Cross-Site Scripting via Shortcode

Read the full analysis

Vulnerability Records

1 records


2024-12-06 00:00	WP-SVG <= 0.9 - Authenticated (Contributor+) Stored Cross-Site Scripting via Shortcode WP-SVG <= 0.9	`CVE-2024-11644`	6.4 Medium	Bob Matyas	No

Showing 1–1 of 1 reports

Plugin Profile

Latestv0.9

WP-SVG

Author

salko

0.0(0)

0/100

Last Updated

2012-01-22 (15y ago)

Active Installs

10+

Downloads

2,764

Requires WP

3.0+

Requires PHP

Tested up to

WP 3.3.2

Created

2012-01-22 (15y ago)

It uses SVGWEB (http://code.google.com/p/svgweb/) project to provide cross-browser SVG support. SVG is vector format for web http://en.wikipedia.org/wiki/Scalable_Vector_Graphics How to use: Simple put a shortcode: [svg scr=/path_to_your_svg/my.svg width=100 height=100] src – path to svg file width – width in pixels height – height in pixels

View on WordPress.org