First published: Mon Jun 03 2019(Updated: )
An issue was discovered in Django 1.11 before 1.11.21, 2.1 before 2.1.9, and 2.2 before 2.2.2. The clickable Current URL value displayed by the AdminURLFieldWidget displays the provided value without validating it as a safe URL. Thus, an unvalidated value stored in the database, or a value provided as a URL query parameter payload, could result in an clickable JavaScript link.
Credit: cve@mitre.org cve@mitre.org
Affected Software | Affected Version | How to fix |
---|---|---|
Djangoproject Django | >=1.11<1.11.21 | |
Djangoproject Django | >=2.1<2.1.9 | |
Djangoproject Django | >=2.2<2.2.2 | |
debian/python-django | 2:2.2.28-1~deb11u2 3:3.2.19-1+deb12u1 3:4.2.16-1 | |
pip/Django | >=2.2a1<2.2.2 | 2.2.2 |
pip/Django | >=2.1a1<2.1.9 | 2.1.9 |
pip/Django | >=1.11a1<1.11.21 | 1.11.21 |
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
The severity of CVE-2019-12308 is medium with a severity value of 6.1.
Django versions 1.11 before 1.11.21, 2.1 before 2.1.9, and 2.2 before 2.2.2 are affected by CVE-2019-12308.
To fix CVE-2019-12308, upgrade Django to version 2.2.2, 2.1.9, or 1.11.21 depending on the version currently installed.
You can find more information about CVE-2019-12308 on the NIST National Vulnerability Database (NVD), the Openwall OSS Security mailing list, and the Django official documentation.
CVE-2019-12308 is classified under CWE-79, which is Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting').