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.
Loading...
Loading...
Score elevated to 9.8 because EPSS predicts 90% probability of exploitation within the next 30 days (top 0.4% of all CVEs). NVD baseline CVSS 9.8 retained for reference. Confidence: see factors.
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.
July 2, 2021
November 21, 2024
| Package | Vulnerable range | Fixed in | Dependents |
|---|---|---|---|
| django | 3.1 ... 3.2.4 (18 versions) | 3.2.5 | — |
MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.
Every time one of our enrichment pipelines (NVD, MITRE cvelistV5, EPSS, CISA KEV, GHSA, OSV, vendor advisories) ran against this CVE. Most recent first.
Working exploit code is in the public domain (3 GitHub PoCs). Defenders should treat patch urgency accordingly — public PoCs typically lead to mass-exploitation within 24-72 hours.
A basic analysis about CVE-2021-35942. SQL injection in Django.
Open source ↗SQL injection via unsanitized QuerySet.order_by() input
Open source ↗See which npm, PyPI, Go, and Maven packages are affected by CVE-2021-35042
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.