Django 1.11.5 release notes¶
September 5, 2017
Django 1.11.5 fixes a security issue and several bugs in 1.11.4.
CVE-2017-12794: Possible XSS in traceback section of technical 500 debug page¶
In older versions, 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.
- Fixed GEOS version parsing if the version has a commit hash at the end (new in GEOS 3.6.2) (#28441).
- Added compatibility for
- Fixed select widget rendering when option values are tuples (#28502).
- Django 1.11 inadvertently changed the sequence and trigger naming scheme on
Oracle. This causes errors on INSERTs for some tables if
'use_returning_into': Falseis in the
DATABASES. The pre-1.11 naming scheme is now restored. Unfortunately, it necessarily requires an update to Oracle tables created with Django 1.11.[1-4]. Use the upgrade script in #28451 comment 8 to update sequence and trigger names to use the pre-1.11 naming scheme.
- Added POST request support to
LogoutView, for equivalence with the function-based
- Fixed a regression where
SelectDateWidgetlocalized the years in the select box (#28530).
- Fixed a regression in 1.11.4 where
runservercrashed with non-Unicode system encodings on Python 2 + Windows (#28487).
- Fixed a regression in Django 1.10 where changes to a
ManyToManyFieldweren’t logged in the admin change history (#27998) and prevented
ManyToManyFieldinitial data in model forms from being affected by subsequent model changes (#28543).
- Fixed non-deterministic results or an
AssertionErrorcrash in some queries with multiple joins (#26522).
- Fixed a regression in
logout()views where they ignored positional arguments (#28550).