CVE-2019-15486 json
Cross-site Scripting in django-js-reverse
published 2019-08-23 7 y ago modified 2026-06-17 4 mo ago also GHSA-vx6v-2rg6-865h , PYSEC-2019-19 , EUVD-2019-0032
- cvss
- 6.1
- version 3.0, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 1.0%
- EPSS 1.0% chance of exploitation in 30 days, percentile 64%
- public exploits
- 0
- none known
Summary
django-js-reverse (aka Django JS Reverse) before 0.9.1 has XSS via js_reverse_inline.
Patch / fix
- pypi django-js-reverse 0.9.1
- django_js_reverse_project django_js_reserve 0.9.1
Exploit prediction
1.04% chance of exploitation in the next 30 days, higher than 64% of all scored CVEs (FIRST EPSS, 2026-11-08).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| NVD | 3.0 | 6.1 | CVSS:3.0/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N |
| NVD | 2.0 | 4.3 | AV:N/AC:M/Au:N/C:N/I:P/A:N |
| GitHub | 3.0 | 6.1 | CVSS:3.0/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N |
Affected packages
| ecosystem | package | affected | fixed in |
|---|---|---|---|
| pypi | django-js-reverse | <0.9.1 |
0.9.1 |
Classification
- Weakness
-
- CWE-79 Improper Neutralization of Input During Web Page Generation
References
-
github.com
/ierror/django-js-reverse/pull/81
web, third-party-advisory
-
github.com
/ierror/django-js-reverse/compare/v0.9.0...v0.9.1
web, patch, release-notes, third-party-advisory
-
github.com
/ierror/django-js-reverse/commit/78d6aff2276f2d341f643b095515f8aaba5e67c2
web
-
github.com
/ierror/django-js-reverse/commit/a3b57d1e4424e2fadabcd526d170c4868d55159c
web
-
nvd.nist.gov
/vuln/detail/CVE-2019-15486
advisory
-
github.com
/advisories/GHSA-vx6v-2rg6-865h
advisory
-
github.com
/ierror/django-js-reverse
package
-
github.com
/pypa/advisory-database/tree/main/vulns/django-js-reverse/PYSEC-2019-19.yaml
web
Sources
- CVE List CVE-2019-15486
- GitHub Advisory GHSA-vx6v-2rg6-865h
- NVD CVE-2019-15486
- OSV PYSEC-2019-19
Fencer Vulns keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.