Public exploit available
Public proof-of-concept or exploit code exists (ExploitDB / Metasploit / Nuclei).

CVE-2021-35042SQL Injection in Django

CWE-89SQL Injection8 documents7 sources
Severity
9.8CRITICALNVD
EPSS
90.0%
top 0.42%
CISA KEV
Not in KEV
Exploit
PoC available
Public exploit / PoC exists
Timeline
PublishedJul 2
Latest updateSep 22

Description

Django 3.1.x before 3.1.13 and 3.2.x before 3.2.5 allows QuerySet.order_by SQL injection if order_by is untrusted input from a client of a web application.

CVSS vector

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:HExploitability: 3.9 | Impact: 5.9

Affected Packages2 packages

NVDdjangoproject/django3.13.1.13+1
PyPIdjangoproject/django3.13.1.13+3

Also affects: Fedora 34

Patches

🔴Vulnerability Details

4
GHSA
SQL Injection in Django2021-09-22
OSV
SQL Injection in Django2021-09-22
OSV
CVE-2021-35042: Django 32021-07-02
CVEList
CVE-2021-35042: Django 32021-07-02

💥Exploits & PoCs

1
Nuclei
Django QuerySet.order_by - SQL Injection

📋Vendor Advisories

2
Red Hat
django: potential SQL injection via unsanitized QuerySet.order_by() input2021-07-01
Debian
CVE-2021-35042: python-django - Django 3.1.x before 3.1.13 and 3.2.x before 3.2.5 allows QuerySet.order_by SQL i...2021
CVE-2021-35042 — SQL Injection in Djangoproject Django | cvebase