CVE-2024-11847 — wp-svg-upload
MEDIUMCVE-2024-11847 is a medium-severity (CVSS 4.8) Cross-site Scripting (XSS) vulnerability in digimix/wp-svg-upload. The records list no fixed version yet; check the vendor advisory below and apply the mitigations in the meantime.
wp-svg-upload WordPress plugin vulnerable to Stored Cross-site Scripting
Exploitation Status
Proof-of-concept exploit code exists
- CISA’s SSVC triage found public proof-of-concept exploit code for this CVE, though no confirmed active exploitation.
Exploitation and automatability from CISA’s SSVC triage for CVE-2024-11847.
EPSS Exploitation Probability
Probability of exploitation in the next 30 days, from FIRST.org EPSS.
How urgent is this, really
Where this sits among everything scored
Real-World Exposure
digimix/wp-svg-uploadReal-time download stats are indexed for npm and PyPI packages. This vulnerability affects Packagist packages — download data is not available via public APIs for these ecosystems.
Description
The wp-svg-upload WordPress plugin through 1.0.0 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.
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| 🐘Packagist | digimix/wp-svg-upload | all versions | No fix |
Affected Products
wp svg uploadwp_svg_upload_projectDetection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for digimix/wp-svg-upload, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Remediation status
The records we use list no patched version of digimix/wp-svg-upload for CVE-2024-11847. Check the maintainer's advisory, and where your build allows, override or pin the dependency away from the vulnerable range.
Mitigate without a patch
Escape or sanitise the affected output on the server side rather than relying on client-side filtering, and add a Content-Security-Policy that blocks inline script execution so injected markup cannot run even if it reaches the page.
Frequently Asked Questions
Is CVE-2024-11847 in your dependencies?
Find it across Packagist, including transitive dependencies.