CVE-2019-10772 json
Sanitizer bypass in svg-sanitizer
published 6y ago modified last mo. also GHSA-8rc5-hx3v-2jg7 , EUVD-2020-0296
- cvss
- 6.1
- version 3.1, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.7%
- EPSS 0.7% chance of exploitation in 30 days, percentile 54%
- public exploits
- 0
- none known
Summary
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.
Patch / fix
- packagist enshrined/svg-sanitize 0.13.1
- svg-sanitizer_project svg-sanitizer 0.13.1
Is CVE-2019-10772 in your dependencies? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.
Check with FencerExploit prediction
0.74% chance of exploitation in the next 30 days, higher than 54% of all scored CVEs (FIRST EPSS, 2026-11-09).
Exploits and checks
- snyk.io https://snyk.io/vuln/SNYK-PHP-ENSHRINEDSVGSANITIZE-536969 referenced PoC, tagged "exploit" by a source, unverified
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| NVD | 3.1 | 6.1 | CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N |
| NVD | 2.0 | 4.3 | AV:N/AC:M/Au:N/C:N/I:P/A:N |
| GitHub | 3.1 | 6.1 | CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N |
Affected packages
| ecosystem | package | affected | fixed in |
|---|---|---|---|
| packagist | enshrined/svg-sanitize | <0.13.1 |
0.13.1 |
Affected products
- n/a enshrined/svg-sanitize
Classification
- Weakness
-
- CWE-79 Improper Neutralization of Input During Web Page Generation
References
-
github.com
/darylldoyle/svg-sanitizer/commit/6add43e5c5649bc40e3afcb68c522720dcb336f9
web
-
snyk.io
/vuln/SNYK-PHP-ENSHRINEDSVGSANITIZE-536969
web, exploit, third-party-advisory
-
nvd.nist.gov
/vuln/detail/CVE-2019-10772
advisory
Sources
- CVE List CVE-2019-10772
- GitHub Advisory GHSA-8rc5-hx3v-2jg7
- NVD CVE-2019-10772
Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.