Is enshrined/svg-sanitize vulnerable?

Composer enshrined/svg-sanitize has 7 known advisories in the phpwarden feed. Feed 2026.10.29.3, updated 2026-10-29.

7advisories
0critical
0on CISA KEV
0no fix recorded
CVETitleSeverityCVSSAffectedFixed in
CVE-2019-18857XSS in enshrined/svg-sanitize due to mishandled script and data values in attributeshigh7.5<0.12.00.12.0
CVE-2019-10772Sanitizer bypass in svg-sanitizermedium6.1<0.13.10.13.1
CVE-2022-23638Cross-site Scripting in enshrined/svg-sanitizemedium6.2<0.15.00.15.0
CVE-2026-107379enshrined/svg-sanitize: Denial of Service via DTD Attribute Declaration Crashmedium6.5<1.0.01.0.0
CVE-2025-55166svg-sanitizer Bypasses Attribute Sanitizationmedium0.0<0.22.00.22.0
CVE-2026-107381svg-sanitizer: Mixed-case xlink:HrEf skips the `<use>` nesting-DoS check in Resolver::processReferencesmedium6.5<1.0.01.0.0
CVE-2026-107380enshrined/svg-sanitize: Stored XSS via DTD Entity / HTML5 Named Character Reference Collisionmedium5.4<1.0.01.0.0

Am I affected?

Find out in one command. phpwarden checks your composer.lock against this advisory and 20,000+ others, ranked by real-world exploitation (CISA KEV + EPSS). Free, offline, open data.

# PHP projects (recommended)
composer require --dev phpwarden/phpwarden
# then
vendor/bin/phpwarden deps composer.lock

# or, without Composer
pipx install phpwarden   &&   phpwarden deps composer.lock

Or keep it checked automatically: GitHub Action · pre-commit hook · GitLab CI · Laravel artisan command

Install docs   How findings are ranked
A version is vulnerable when it falls inside an affected range and below the fixed version. phpwarden applies these ranges to the exact versions in your lockfile or install, so you only see what applies to you.