CVE-2017-12794: XSS

Published Sep 7, 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.

Other sources

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.

GitHub

Affected Software

16 affected componentsFixes available
pip/Django>=1.11a1<1.11.5
1.11.5
pip/Django>=1.10a1<1.10.8
1.10.8
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
debian/python-django
2:2.2.28-1~deb11u22:2.2.28-1~deb11u123:3.2.25-0+deb12u33:3.2.25-0+deb12u23:4.2.28-0+deb13u23:4.2.28-0+deb13u13:5.2.16-1

Remediation

Recommended actions to resolve this vulnerability, in priority order.

  1. Upgrade

    Upgrade pip/Django to a version that resolves this vulnerability.

    Fixed in 1.11.5
  2. Upgrade

    Upgrade pip/Django to a version that resolves this vulnerability.

    Fixed in 1.10.8
  3. Upgrade

    Upgrade debian/python-django to a version that resolves this vulnerability.

    Fixed in 2:2.2.28-1~deb11u2Fixed in 2:2.2.28-1~deb11u12Fixed in 3:3.2.25-0+deb12u3Fixed in 3:3.2.25-0+deb12u2Fixed in 3:4.2.28-0+deb13u2Fixed in 3:4.2.28-0+deb13u1Fixed in 3:5.2.16-1
  4. Upgrade

    Upgrade Django to a version that resolves this vulnerability.

    Fixed in 1.10.8
  5. Upgrade

    Upgrade Django to a version that resolves this vulnerability.

    Fixed in 1.11.5
  6. Configuration

    Ensure DEBUG is not enabled in production (vulnerability affects the technical 500 debug page when DEBUG=True makes it accessible).

    Django DEBUG = False

Event History

Sep 7, 2017
CVE Published
via MITRE·01:00 PM
Data Sourced
via MITRE·01:00 PM
Description
Data Sourced
via NVD·01:29 PM
RemedyDescriptionSeverityWeaknessAffected Software
Jan 4, 2019
Advisory Published
via GitHub·05:50 PM
Jan 11, 2024
Data Sourced
via Launchpad·10:27 PM
Description
Feb 20, 2026
Data Sourced
via Ubuntu·08:39 PM
RemedyDescriptionSeverityAffected Software
Jul 16, 2026
Data Sourced
via Debian·11:14 AM
DescriptionAffected Software
Free Weekly Intel

Don't miss critical vulnerabilities

Join thousands of security professionals who receive our weekly digest of trending CVEs, zero-days, and exploited vulnerabilities.

No spam. Unsubscribe anytime.

Frequently Asked Questions

1

What is CVE-2017-12794?

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.

2

How severe is CVE-2017-12794?

CVE-2017-12794 has a severity rating of 6.1 (medium).

3

How does CVE-2017-12794 affect production sites?

CVE-2017-12794 is not expected to affect most production sites, as they should have HTML autoescaping enabled.

4

How can I fix CVE-2017-12794?

To fix CVE-2017-12794, upgrade to Django version 1.10.8 or 1.11.5 or later.

5

Where can I find more information about CVE-2017-12794?

More information about CVE-2017-12794 can be found at the official Django website and security advisory.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203