Django’s development team is strongly committed to responsible reporting and disclosure of security-related issues, as outlined in Django’s security policies.
As part of that commitment, we maintain the following historical list of issues which have been fixed and disclosed. For each issue, the list below includes the date, a brief description, the CVE identifier if applicable, a list of affected versions, a link to the full disclosure and links to the appropriate patch(es).
Some important caveats apply to this information:
Lists of affected versions include only those versions of Django which had stable, security-supported releases at the time of disclosure. This means older versions (whose security support had expired) and versions which were in pre-release (alpha/beta/RC) states at the time of disclosure may have been affected, but are not listed.
The Django project has on occasion issued security advisories, pointing out potential security problems which can arise from improper configuration or from other issues outside of Django itself. Some of these advisories have received CVEs; when that is the case, they are listed here, but as they have no accompanying patches or releases, only the description, disclosure and CVE will be listed.
All security issues have been handled under versions of Django’s security process. These are listed below.
Denial-of-service possibility in django.utils.text.Truncator.
Full description
Potential denial of service vulnerability in
django.utils.encoding.uri_to_iri(). Full description
Potential regular expression denial of service vulnerability in
EmailValidator/URLValidator. Full description
Potential bypass of validation when uploading multiple files using one form field. Full description
Potential denial-of-service vulnerability in file uploads. Full description
Potential denial-of-service via Accept-Language headers. Full description
Potential denial-of-service vulnerability in internationalized URLs. Full description
Potential reflected file download vulnerability in FileResponse. Full description
Potential SQL injection via Trunc(kind) and Extract(lookup_name)
arguments. Full description
Potential SQL injection in QuerySet.annotate(), aggregate(), and
extra(). Full description
Potential SQL injection via QuerySet.explain(**options) on PostgreSQL.
Full description
Possible XSS via {% debug %} template tag. Full description
Denial-of-service possibility in file uploads. Full description
Potential directory-traversal via Storage.save(). Full description
Potential information disclosure in dictsort template filter. Full
description
Denial-of-service possibility in UserAttributeSimilarityValidator. Full
description
Potential bypass of an upstream access control based on URL paths. Full description
Potential SQL injection via unsanitized QuerySet.order_by() input. Full
description
Potential directory traversal via admindocs. Full description
Possible indeterminate SSRF, RFI, and LFI attacks since validators accepted leading zeros in IPv4 addresses. Full description
Header injection possibility since URLValidator accepted newlines in input
on Python 3.9.5+. Full description
Potential directory-traversal via uploaded files. Full description
Potential directory-traversal via uploaded files. Full description
Web cache poisoning via django.utils.http.limited_parse_qsl(). Full
description
Potential directory-traversal via archive.extract(). Full description
Permission escalation in intermediate-level directories of the file system cache on Python 3.7+. Full description
Incorrect permissions on intermediate-level directories on Python 3.7+. Full description
Possible XSS via admin ForeignKeyRawIdWidget. Full description
Potential data leakage via malformed memcached keys. Full description
Potential SQL injection via tolerance parameter in GIS functions and
aggregates on Oracle. Full description
Potential SQL injection via StringAgg(delimiter). Full description
Potential account hijack via password reset form. Full description
Privilege escalation in the Django admin. Full description
Potential memory exhaustion in django.utils.encoding.uri_to_iri(). Full
description
SQL injection possibility in key and index lookups for
JSONField/HStoreField. Full description
Denial-of-service possibility in strip_tags(). Full description
Denial-of-service possibility in django.utils.text.Truncator. Full
description
Incorrect HTTP detection with reverse-proxy connecting via HTTPS. Full description
XSS via “Current URL” link generated by AdminURLFieldWidget. Full
description
Prototype pollution in bundled jQuery. Full description
Memory exhaustion in django.utils.numberformat.format(). Full description
Django 2.1 (patch)
Django 2.0 (patch and correction)
Django 1.11 (patch)
Content spoofing possibility in the default 404 page. Full description
Password hash disclosure to “view only” admin users. Full description
Django 2.1 (patch)
Open redirect possibility in CommonMiddleware. Full description
Denial-of-service possibility in truncatechars_html and
truncatewords_html template filters. Full description
Denial-of-service possibility in urlize and urlizetrunc template
filters. Full description
Information leakage in AuthenticationForm. Full description
Possible XSS in traceback section of technical 500 debug page. Full description
Open redirect vulnerability in django.views.static.serve(). Full
description
Open redirect and possible XSS attack via user-supplied numeric redirect URLs. Full description
DNS rebinding vulnerability when DEBUG=True. Full description
User with hardcoded password created when running tests on Oracle. Full description
CSRF protection bypass on a site with Google Analytics. Full description
XSS in admin’s add/change related popup. Full description
User enumeration through timing difference on password hasher work factor upgrade. Full description
Malicious redirect and possible XSS attack via user-supplied redirect URLs containing basic auth. Full description
User with “change” but not “add” permission can create objects for
ModelAdmin’s with save_as=True. Full description
Django 1.9 (patch)
Settings leak possibility in date template filter. Full description
Denial-of-service possibility in logout() view by filling session store.
Full description
Denial-of-service possibility in URL validation. Full description
Django 1.8 (patch)
Header injection possibility since validators accept newlines in input. Full description
Denial-of-service possibility by filling session store. Full description
Fixed session flushing in the cached_db backend. Full description
Django 1.8 (patch)
Mitigated possible XSS attack via user-supplied redirect URLs. Full description
Denial-of-service possibility with strip_tags(). Full description
XSS attack via properties in ModelAdmin.readonly_fields. Full description
Database denial-of-service with ModelMultipleChoiceField. Full description
Denial-of-service attack against django.views.static.serve(). Full
description
Mitigated possible XSS attack via user-supplied redirect URLs. Full description
WSGI header spoofing via underscore/dash conflation. Full description
Data leakage via querystring manipulation in admin. Full description
RemoteUserMiddleware session hijacking. Full description
File upload denial of service. Full description
reverse() can generate URLs pointing to other hosts. Full description
Malformed URLs from user input incorrectly validated. Full description
Caches may be allowed to store and serve private data. Full description
MySQL typecasting causes unexpected query results. Full description
Caching of anonymous pages could reveal CSRF token. Full description
Unexpected code execution using reverse(). Full description
Denial-of-service via large passwords. Full description
Django 1.4 (patch and Python compatibility fix)
Django 1.5 (patch)
Directory-traversal via ssi template tag. Full description
Possible XSS via unvalidated URL redirect schemes. Full description
XSS via admin trusting URLField values. Full description
Django 1.5 (patch)
Denial-of-service via formset max_num bypass. Full description
Information leakage via admin history log. Full description
Entity-based attacks against Python XML libraries. Full description
Additional hardening of Host header handling. Full description
Additional hardening of redirect validation. Full description
Additional hardening of Host header handling. Full description
Host header poisoning. Full description
Denial-of-service via large image files. Full description
Denial-of-service via compressed image files. Full description
XSS via failure to validate redirect scheme. Full description
Potential CSRF via Host header. Full description
This notification was an advisory only, so no patches were issued.
Django 1.2
Django 1.3
Host header cache poisoning. Full description
Information leakage/arbitrary request issuance via URLField.verify_exists.
Full description
Denial-of-service via URLField.verify_exists. Full description
Session manipulation when using memory-cache-backed session. Full description
Directory-traversal on Windows via incorrect path-separator handling. Full description
XSS via unsanitized names of uploaded files. Full description
CSRF via forged HTTP headers. Full description
Denial-of-service in password-reset mechanism. Full description
Information leakage in administrative interface. Full description
XSS via trusting unsafe cookie value. Full description
Django 1.2 (patch)
Denial-of-service via pathological regular expression performance. Full description
Directory-traversal in development server media handler. Full description
CSRF via preservation of POST data during admin login. Full description
XSS via admin login redirect. Full description
Denial-of-service via arbitrarily-large Accept-Language header. Full
description
Some security issues were handled before Django had a formalized security process in use. For these, new releases may not have been issued at the time and CVEs may not have been assigned.
Apparent “caching” of authenticated user. Full description
Django 0.95 (patch)
Filename validation issue in translation framework. Full description
Dec 25, 2023