Django Cross-site scripting (XSS) vulnerability

Denial-of-service in Django

Django has Inefficient Algorithmic Complexity

Django Template Engine Vulnerable to XSS

Django Denial of Service Vulnerability in the authentication framework

Django cross-site scripting (XSS) vulnerability in the AdminURLFieldWidget widget

Django Access Restrictions Bypass

Denial of service in django

Django: cache middleware may expose private responses when unrelated request cookies are present

Django DNS Rebinding Vulnerability

Django open redirect and possible XSS attack via user-supplied numeric redirect URLs

Django has Inefficient Algorithmic Complexity

Improper Input Validation in Django

Django has Observable Timing Discrepancy

Resource exhaustion in Django

SQL Injection in Django

Django Denial-of-service possibility in truncatechars_html and truncatewords_html template filters

An issue was discovered in Django 5.2 before 5.2.17 and 6.0 before 6.0.8. `django.utils.translation.check_for_language()` is subject to a potential denial-of-service attack when given many distinct, very long language codes, which are retained as keys in an in-memory cache and consume process memory. Such codes reach the function through the `django.views.i18n.set_language()` view, which is not routed by default. The consumed memory is bounded, since request data is limited by the `DATA_UPLOAD_MAX_MEMORY_SIZE` setting (default 2.5 MB) and the cache holds a fixed maximum number of entries. Earlier, unsupported Django series (such as 5.1.x, 5.0.x, and 4.2.x) were not evaluated and may also be affected. Django would like to thank Jaeyoung Jang for reporting this issue.

Django denial of service via file upload naming

Django Allows Arbitrary URL Generation