CVE-2020-9402High· 8.8▾ TwilightSQL injection in Django
▾ Twilight zone — High severity, or a signal on a lesser flaw
impact 48.4 · likelihood 4.5 · exploitation 0
Need a working PoC? Pro members can cast a request and our team develops one — it lands right here.
Exploit-prediction probability, daily snapshots since Jul 9.
Disclosure to exploitation, from the record and what we observed since indexing it.
Disclosed via OSV
Last analysed / modified upstream
23%
Django 1.11 before 1.11.29, 2.2 before 2.2.11, and 3.0 before 3.0.4 allows SQL Injection if untrusted data is used as a tolerance parameter in GIS functions and aggregates on Oracle. By passing a suitably crafted tolerance to GIS functions and aggregates on Oracle, it was possible to break escaping and inject malicious SQL.
django >= 1.11, < 1.11.29django >= 2.2, < 2.2.11django >= 3.0, < 3.0.4Upgrade to a patched release:
django 1.11.29django 2.2.11django 3.0.4Connected by shared product, vendor, weakness, or advisory.
CVE-2026-5766Medium· 5.3Django has an Improper Handling of Length Parameter Inconsistency
CVE-2024-27351Medium· 5.3Regular expression denial-of-service in Django
CVE-2025-64460MediumDjango is vulnerable to DoS via XML serializer text extraction
CVE-2025-13372Medium· 4.3Django is vulnerable to SQL injection in column aliases
CVE-2025-64458High· 7.5Django has a denial-of-service vulnerability in HttpResponseRedirect and HttpResponsePermanentRedirect on Windows
CVE-2024-38875High· 7.5Django vulnerable to Denial of Service