Django: has_vary_header may expose cached responses when Vary values contain whitespace

Django vulnerable to Reflected File Download attack

An issue was discovered in Django 5.2 before 5.2.17 and 6.0 before 6.0.8. `django.contrib.admin.utils.display_for_field()` renders `URLField` values as clickable links in the admin without validating the URL. A value stored with an unsafe scheme is displayed as a link on changelist and read-only admin pages, which allows cross-site scripting against staff users who click the link. Exploitation requires the unsafe value to already be stored in the database. `URLField` validation through a `ModelForm` or the admin rejects unsafe schemes, so this affects applications that persist `URLField` data without running model validation, for example through direct queryset writes, deserialization, or bulk import of untrusted input. Django would like to thank Egor Saltykov for reporting this issue.

Django: DomainNameValidator permits newline characters that may enable HTTP header injection

Django vulnerable to Uncontrolled Resource Consumption

Cross-site scripting in django

Django has a denial-of-service possibility in strip_tags()

Django: UpdateCacheMiddleware may disclose cached responses due to case-sensitive Cache-Control handling

Information disclosure in Django

Django Reuses Cached CSRF Token

Django denial-of-service in django.utils.html.strip_tags()

Django Improper Output Neutralization for Logs vulnerability

Improper date handling in Django

Django Cross-site Scripting in AdminURLFieldWidget

Django WSGI Header Spoofing Vulnerability

Django Denial of service vulnerability in django.utils.encoding.uri_to_iri

Django Uses Persistent Cookies Containing Sensitive Information

Directory traversal in Django

Django cross-site scripting (XSS) attack via user-supplied redirect URLs

Django vulnerable to a denial-of-service attack