Is enshrined/svg-sanitize 0.7 vulnerable?
Composer · 3 releases from 0.7.0 to 0.7.2 · latest enshrined/svg-sanitize is 1.1.1 · checked 18 Nov 2026
Yes: 7 known advisories
Yes. enshrined/svg-sanitize 0.7.2, the last 0.7 release, is affected by 7 known security advisories (1 high, 6 medium), including CVE-2019-18857, CVE-2026-107380, CVE-2026-107381. Upgrade to 1.0.0 or later to fix all of them.
composer require enshrined/svg-sanitize:^1.0.0Is your project on an affected enshrined/svg-sanitize?
Look after several Laravel or PHP apps? Indie watches up to 15 repos, private ones too, for $5 a month. See Indie
Advisories affecting enshrined/svg-sanitize 0.7.2
enshrined/svg-sanitize: Stored XSS via DTD Entity / HTML5 Named Character Reference Collision
- Affected
- <1.0.0
- Fixed in
- 1.0.0
svg-sanitizer: Mixed-case xlink:HrEf skips the `<use>` nesting-DoS check in Resolver::processReferences
- Affected
- <1.0.0
- Fixed in
- 1.0.0
enshrined/svg-sanitize: Denial of Service via DTD Attribute Declaration Crash
- Affected
- <1.0.0
- Fixed in
- 1.0.0
svg-sanitizer Bypasses Attribute Sanitization
- Affected
- <0.22.0
- Fixed in
- 0.22.0
Cross-site Scripting in enshrined/svg-sanitize
- Affected
- <0.15.0
- Fixed in
- 0.15.0
Sanitizer bypass in svg-sanitizer
- Affected
- <0.13.1
- Fixed in
- 0.13.1
XSS in enshrined/svg-sanitize due to mishandled script and data values in attributes
- Affected
- <0.12.0
- Fixed in
- 0.12.0
Every enshrined/svg-sanitize 0.7.x release
Affected: 0.7.0 to 0.7.2. Latest enshrined/svg-sanitize: 1.1.1.
| Version | Known advisories |
|---|---|
| enshrined/svg-sanitize 0.7.2 | CVE-2026-107380, CVE-2026-107381, CVE-2026-107379, CVE-2025-55166, CVE-2022-23638, CVE-2019-10772, CVE-2019-18857 |
| enshrined/svg-sanitize 0.7.1 | CVE-2026-107380, CVE-2026-107381, CVE-2026-107379, CVE-2025-55166, CVE-2022-23638, CVE-2019-10772, CVE-2019-18857 |
| enshrined/svg-sanitize 0.7.0 | CVE-2026-107380, CVE-2026-107381, CVE-2026-107379, CVE-2025-55166, CVE-2022-23638, CVE-2019-10772, CVE-2019-18857 |
Which of your client projects are still on enshrined/svg-sanitize 0.7?
NPMscan reads the lockfiles in every GitHub repo you pick, finds the exact enshrined/svg-sanitize version each one installs, and checks it against these advisories. Each finding comes with the command that fixes it.
Other enshrined/svg-sanitize versions
- enshrined/svg-sanitize 0.10
- enshrined/svg-sanitize 0.9
- enshrined/svg-sanitize 0.8
- enshrined/svg-sanitize 0.6
- enshrined/svg-sanitize 0.5
- enshrined/svg-sanitize 0.4
- enshrined/svg-sanitize 1.1
- enshrined/svg-sanitize 1.0
- enshrined/svg-sanitize 0.22
- enshrined/svg-sanitize 0.21
- enshrined/svg-sanitize 0.20
- enshrined/svg-sanitize 0.19
- All enshrined/svg-sanitize advisories
Advisory data from OSV.dev (opens OSV.dev in a new tab), which includes the GitHub Advisory Database. Release list from the Composer registry. Refreshed daily.