Is enshrined/svg-sanitize 0.19 vulnerable?
Composer · 1 release from 0.19.0 to 0.19.0 · latest enshrined/svg-sanitize is 1.1.1 · checked 18 Nov 2026
Yes: 4 known advisories
Yes. enshrined/svg-sanitize 0.19.0, the last 0.19 release, is affected by 4 known security advisories (4 medium), including CVE-2026-107380, CVE-2026-107381, CVE-2026-107379. 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.19.0
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
Which of your client projects are still on enshrined/svg-sanitize 0.19?
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
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.