First published: Thu Sep 07 2017(Updated: )
In Django 1.10.x before 1.10.8 and 1.11.x before 1.11.5, HTML autoescaping was disabled in a portion of the template for the technical 500 debug page. Given the right circumstances, this allowed a cross-site scripting attack. This vulnerability shouldn't affect most production sites since you shouldn't run with "DEBUG = True" (which makes this page accessible) in your production settings.
Credit: cve@mitre.org cve@mitre.org
Affected Software | Affected Version | How to fix |
---|---|---|
Djangoproject Django | =1.10.0 | |
Djangoproject Django | =1.10.1 | |
Djangoproject Django | =1.10.2 | |
Djangoproject Django | =1.10.3 | |
Djangoproject Django | =1.10.4 | |
Djangoproject Django | =1.10.5 | |
Djangoproject Django | =1.10.6 | |
Djangoproject Django | =1.10.7 | |
Djangoproject Django | =1.11.0 | |
Djangoproject Django | =1.11.1 | |
Djangoproject Django | =1.11.2 | |
Djangoproject Django | =1.11.3 | |
Djangoproject Django | =1.11.4 | |
pip/Django | >=1.11a1<1.11.5 | 1.11.5 |
pip/Django | >=1.10a1<1.10.8 | 1.10.8 |
debian/python-django | 2:2.2.28-1~deb11u2 3:3.2.19-1+deb12u1 3:4.2.16-1 |
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
CVE-2017-12794 is a vulnerability in Django versions 1.10.x before 1.10.8 and 1.11.x before 1.11.5 that allows for a cross-site scripting attack.
CVE-2017-12794 has a severity rating of 6.1 (medium).
CVE-2017-12794 is not expected to affect most production sites, as they should have HTML autoescaping enabled.
To fix CVE-2017-12794, upgrade to Django version 1.10.8 or 1.11.5 or later.
More information about CVE-2017-12794 can be found at the official Django website and security advisory.