Vulnerabilities · 2017 · Djangoproject
CVE-2017-12794
Djangoproject Django vulnerability
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.
Affected products
Django. The exact versions are in the references.
What to do now
- Check your exposureFind out whether Djangoproject Django runs anywhere in your environment, including systems of suppliers.
- UpdateInstall the version in which the vendor fixed the vulnerability. The references lead to the advisory.
- Limit access until thenIf you cannot update at once, take the system off the internet or restrict who can reach it.
References
- www.djangoproject.com/weblog/2017/sep/05/security-releases/ · Patch
- www.securityfocus.com/bid/100643 · Third Party Advisory
- www.securitytracker.com/id/1039264 · Third Party Advisory
- usn.ubuntu.com/3559-1/
- nvd.nist.gov/vuln/detail/CVE-2017-12794
- github.com/advisories/GHSA-9r8w-6x8c-6jr9
- web.archive.org/web/20170927072701/http://www.securitytracker.com/id/1039264
- web.archive.org/web/20200227150819/http://www.securityfocus.com/bid/100643
- nvd.nist.gov/vuln/detail/CVE-2017-12794
- cve.org/CVERecord?id=CVE-2017-12794
More vulnerabilities in Djangoproject products
CVE-2026-1312CVE-2026-1287CVE-2026-1285CVE-2026-1207CVE-2025-64460CVE-2025-64459CVE-2025-64458CVE-2025-59682All 137
Data: CVE list and the NVD. This product uses data from the NVD API but is not endorsed or certified by the NVD.