How severe is CVE-2024-11184?

CVE-2024-11184 has a CVSS score of 4.8/10, rated MEDIUM. Review your exposure and patch according to your risk tolerance.

Which packages are affected by CVE-2024-11184?

CVE-2024-11184 affects the following packages: mwdelaney/wp-enable-svg (Packagist). Ecosystems affected: Packagist.

How do I fix CVE-2024-11184?

The records we use list no patched version of mwdelaney/wp-enable-svg for CVE-2024-11184. Check the maintainer's advisory, and where your build allows, override or pin the dependency away from the vulnerable range.

How do I detect CVE-2024-11184 in my Packagist dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for mwdelaney/wp-enable-svg, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

How do I mitigate CVE-2024-11184 if there is no patch (or I can't update yet)?

If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

Is CVE-2024-11184 actively exploited in the wild?

No public exploit code has been indexed for CVE-2024-11184 yet. This does not mean the vulnerability cannot be exploited — absence of public exploits does not imply safety. Apply the recommended fix and use O3 Security to monitor your exposure.

What is the EPSS score for CVE-2024-11184?

CVE-2024-11184 has an EPSS (Exploit Prediction Scoring System) score of 0.4%, placing it in the 37th percentile of all CVEs. EPSS is maintained by FIRST.org and estimates the probability that a vulnerability will be exploited in the wild within the next 30 days. This score indicates relatively lower exploitation probability, though the CVSS severity should still guide your patching priority.

When was CVE-2024-11184 published, and has it been updated?

CVE-2024-11184 was published on January 2, 2025 and was last updated on February 7, 2025. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

🐘

🐘 Packagist

Not in CISA KEV

MEDIUM severity

CVE-2024-11184 — wp-enable-svg

MEDIUM

CVE-2024-11184 is a medium-severity (CVSS 4.8) vulnerability in mwdelaney/wp-enable-svg. The records list no fixed version yet; check the vendor advisory below and apply the mitigations in the meantime.

The wp-enable-svg WordPress plugin does not sanitize SVG files when uploaded

Published

Jan 2, 2025

Updated

Feb 7, 2025

Affected

1 pkg

Patched

See advisory

Exploits

None indexed

Exploitation data as of Nov 5, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

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-11184.

EPSS Exploitation Probability

via FIRST.org ↗

0.4%probability of exploitation in next 30 days

Lower Risk0.00%

Lower risk than most CVEs37th percentile — riskier than 37% of all scored CVEsHighest risk

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

1 pkg affected

🐘mwdelaney/wp-enable-svg

Real-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-enable-svg WordPress plugin through 0.2 does not sanitize SVG files when uploaded, allowing for authors and above to upload SVGs containing malicious scripts

Affected Packages

1 total

Ecosystem	Package	Vulnerable range	Fix
🐘Packagist	`mwdelaney/wp-enable-svg`	all versions	No fix

Affected Products

1 product · 1 configurations

Application

wp enable svgwp_enable_svg_project

≤ 0.7

range

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for mwdelaney/wp-enable-svg, 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 mwdelaney/wp-enable-svg for CVE-2024-11184. Check the maintainer's advisory, and where your build allows, override or pin the dependency away from the vulnerable range.
Mitigate without a patch
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

Frequently Asked Questions

The wp-enable-svg WordPress plugin through 0.2 does not sanitize SVG files when uploaded, allowing for authors and above to upload SVGs containing malicious scripts

O3 Security · Impact-Aware SCA

Is CVE-2024-11184 in your dependencies?

Find it across Packagist, including transitive dependencies.

Scan my dependencies How O3 SCA works