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.
| Product | Vendor Advisory | Solution File | Added | Published |
|---|---|---|---|---|
| Alpine Linux | — | Upgrade py-djangoUpgrade py3-django | Aug 3, 2018 | Sep 7, 2017 |
| Debian | — | Upgrade python-django | Jul 30, 2024 | Sep 7, 2017 |
| Freebsd | — | Upgrade py27-django111Upgrade py34-django110Upgrade py35-django110Upgrade py36-django111Upgrade py35-django111Upgrade py36-django110Upgrade py34-django111Upgrade py27-django110 | Sep 7, 2017 | Sep 6, 2017 |
| Oracle Solaris | — | Upgrade library/python/django-27 to version 1.11.16-11.4.4.0.1.1.0 on Solaris 11.4Upgrade library/python/django to version 1.11.16-11.4.4.0.1.1.0 on Solaris 11.4 | Dec 17, 2018 | Sep 7, 2017 |
| Suse | — | Upgrade python-django | Mar 28, 2018 | Sep 7, 2017 |
| Ubuntu | — | Upgrade python3-djangoUpgrade python-django | Feb 8, 2018 | Sep 7, 2017 |
With curated Threat Intelligence, you can see which vulnerabilities truly put you at risk, prioritize what matters most, and act before attackers do.
Explore Intelligence Hub