CVE-2024-4269: The SVG Block WordPress plugin before 1.1.20 does not sanitize SVG file contents, which enables users with at
CVE-2024-4269 is a medium-severity flaw (CVSS 6.1) affecting svg block. Below: why it ranks where it does, which versions are affected, what to do, and the exact commands.
The SVG Block WordPress plugin before 1.1.20 does not sanitize SVG file contents, which enables users with at least the author role to SVG with malicious JavaScript to conduct Stored XSS attacks.
Why this priority
- Public exploit reference
A fixed release or distro patch exists.
Risk facts
| CVSS score | 6.1 (Medium) |
| Attack vector | Network (remote) |
| Attack complexity | Low |
| Privileges needed | None |
| User interaction | Required |
| EPSS exploit chance | 0.4% (top 64%) |
| CISA exploited list | No |
| Weakness | CWE-79 |
| Published | 2024-07-13 |
| Last modified | 2026-06-17 |
Last updated 2026-06-17 · Sources: CVE Program, NVD, CISA KEV, EPSS and vendor advisories · How we score
Am I affected?
Timeline
- Published CVE record published
- Updated Record last modified
Scores and fixes here are computed automatically from those and other public sources. Confirm with the vendor advisory before changing production systems.
Quick answers
How do I fix CVE-2024-4269?
svg block: upgrade to 1.1.20. Exact commands for each OS are on this page.
Is CVE-2024-4269 being exploited?
CVE-2024-4269 is not on the CISA Known Exploited Vulnerabilities list at the time of the last update. Check again, as this can change.
What does CVE-2024-4269 affect?
CVE-2024-4269 affects svg block. Severity is medium (CVSS 6.1). The SVG Block WordPress plugin before 1.1.20 does not sanitize SVG file contents, which enables users with at least the author role to SVG with malicious JavaScript to conduct Stored XSS attacks.
How urgent is CVE-2024-4269?
Priority 35/100. Public exploit reference