NIST deprecates RSA-2048 from 2030. Find every one of them before attackers do.
🐘
🐘 Packagist
Not in CISA KEV
MEDIUM severity

Sanitizer bypass in svg-sanitizerGHSA-8rc5-hx3v-2jg7

MEDIUMFix: darylldoyle/svg-sanitizer@6add43e

GHSA-8rc5-hx3v-2jg7 is a medium-severity (CVSS 6.1) Cross-site Scripting (XSS) vulnerability in enshrined/svg-sanitize. 1 public exploit or proof-of-concept reference is indexed, so weaponization risk is real. A fix is available for enshrined/svg-sanitize — see the affected versions and patch details below.

Also known asCVE-2019-10772SNYK-PHP-ENSHRINEDSVGSANITIZE-536969
Published
Updated
Affected
1 pkg
Patched
1 / 1
Exploits
1 known
Exploitation data as of Nov 9, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

EPSS Exploitation Probability

via FIRST.org ↗
0.7%probability of exploitation in next 30 days
Lower Risk0.00%
Lower risk than most CVEs55th percentile — riskier than 55% of all scored CVEsHighest risk
0.00%0.41%0.83%1.24%0.2%0.7%May 26Sep 26Nov 26

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
🐘enshrined/svg-sanitize

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

It is possible to bypass enshrined/svg-sanitize before 0.13.1 using the "xlink:href" attribute due to mishandling of the xlink namespace by the sanitizer.

Affected Packages

1 total 1 fixed
EcosystemPackageVulnerable rangeFix
🐘Packagistenshrined/svg-sanitizeall versions0.13.1composer require enshrined/svg-sanitize:^0.13.1

Affected Products

1 product · 1 configurations
Application
svg-sanitizersvg-sanitizer_project
< 0.13.1
range
Exploits & PoCs
1

Research use only. For defensive security, authorized penetration testing, and academic research only. Never execute exploit code against systems without explicit written authorization.

It is possible to bypass enshrined/svg-sanitize before 0.13.1 using the …

snyk.ioNVDDec 2019

Detection & mitigation playbook

Open-source dependency

  1. Detect

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

  2. Fix

    Update enshrined/svg-sanitize to 0.13.1 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-8rc5-hx3v-2jg7 is resolved across your whole dependency graph.

  3. Workarounds

    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

It is possible to bypass enshrined/svg-sanitize before 0.13.1 using the "xlink:href" attribute due to mishandling of the xlink namespace by the sanitizer.
O3 Security · Impact-Aware SCA

Is GHSA-8rc5-hx3v-2jg7 in your dependencies?

Find it across Packagist, including transitive dependencies.

Scan my dependencies How O3 SCA works
Sanitizer bypass in svg-sanitizer (Medium 6.1)