MediumGHSA-8rc5-hx3v-2jg7CVE-2019-10772SNYK-PHP-ENSHRINEDSVGSANITIZE-536969

Sanitizer bypass in svg-sanitizer

Published 27 Feb 2020 · Updated 10 Sept 2026

Is your project on an affected enshrined/svg-sanitize?

Private repo? Upload its lockfile instead, or connect GitHub to check every repo.

Look after several Laravel or PHP apps? Indie watches up to 15 repos, private ones too, for $5 a month. See Indie

Affected package

Affected
<0.13.1
Fixed in
0.13.1
Update to the fixed version for your release line, for example:composer require enshrined/svg-sanitize:^0.13.1

Details

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.

Is GHSA-8rc5-hx3v-2jg7 in any of your client repos?

Checking one package by hand is fine. Checking it across forty client projects is not. NPMscan reads the lockfiles in every GitHub repo you pick, finds each project with an affected enshrined/svg-sanitize, and gives you the command that fixes it.

More advisories for enshrined/svg-sanitize

  • MediumCVE-2026-107380enshrined/svg-sanitize: Stored XSS via DTD Entity / HTML5 Named Character Reference Collision · 8 Oct 2026
  • MediumCVE-2026-107381svg-sanitizer: Mixed-case xlink:HrEf skips the `<use>` nesting-DoS check in Resolver::processReferences · 8 Oct 2026
  • MediumCVE-2026-107379enshrined/svg-sanitize: Denial of Service via DTD Attribute Declaration Crash · 8 Oct 2026
  • MediumCVE-2025-55166svg-sanitizer Bypasses Attribute Sanitization · 12 Aug 2025
  • MediumCVE-2022-23638Cross-site Scripting in enshrined/svg-sanitize · 14 Feb 2022
  • HighCVE-2019-18857XSS in enshrined/svg-sanitize due to mishandled script and data values in attributes · 8 Jan 2020
enshrined/svg-sanitize security overview

References

Advisory data from OSV.dev (opens OSV.dev in a new tab), refreshed daily.