CVE-2020-7471
A public proof of concept exists; no exploitation attested.
- Published2020-02-03
- Fixed in3.0.3 · 2.2.10 · 1.11.28
- WeaknessCWE-89
Am I affected?
Debian, Ubuntu or Red Hat sometimes backport a fix without changing the upstream version number: such a version reads « to verify », never « affected ».With a domain, we read the version its public headers and pages expose. A distribution build can carry the fix under an older number.
Description
Django 1.11 before 1.11.28, 2.2 before 2.2.10, and 3.0 before 3.0.3 allows SQL Injection if untrusted data is used as a StringAgg delimiter (e.g., in Django applications that offer downloads of data as a series of rows with a user-specified column delimiter). By passing a suitably crafted delimiter to a contrib.postgres.aggregates.StringAgg instance, it was possible to break escaping and inject malicious SQL.
Timeline
dates in UTC- 2020-02-0312:15CVE publishedNVD
- 2026-10-2319:23First public proof of conceptPoC-in-GitHub
- 2026-10-2319:23EPSS crossed 10 %FIRST EPSS
Observed activity
isMalicious corpus · updated 2026-10-23 21:37 UTCBlock these indicators
- Firewall list (EDL, text): https://api.ismalicious.com/edl/cve/CVE-2020-7471?format=txt
- CSV export: https://api.ismalicious.com/edl/cve/CVE-2020-7471?format=csv
- TAXII collection of exploited CVEs
- The EDL and CSV take an API key on the Pro plan.
Versions per branch
NVD · OSV| Branch | Affected | Fixed in | Source |
|---|---|---|---|
| 3.0 | ≥ 3.0, < 3.0.3 | 3.0.3 | NVD · OSV |
| 3.0 | ≥ 3.0.0, < 3.0.3 | 3.0.3 | OSV |
| 2.2 | ≥ 2.2, < 2.2.10 | 2.2.10 | NVD · OSV |
| 2.x | ≥ 2.0, < 2.2.10 | 2.2.10 | OSV |
| 2.2 | ≥ 2.2.0, < 2.2.10 | 2.2.10 | OSV |
| 1.11 | ≥ 1.11, < 1.11.28 | 1.11.28 | NVD · OSV |
| 1.11 | < 1.11.28 | 1.11.28 | OSV |
| 1.11 | ≥ 1.11.0, < 1.11.28 | 1.11.28 | OSV |
as publishedRanges as NVD and OSV publish them; a distribution’s build can be fixed under an older number.
Fix
- Update Django to 3.0.3 · 2.2.10 · 1.11.28
Advisories and patches
- docs.djangoproject.comVendor Advisory
- github.comPatch
- www.djangoproject.comVendor Advisory
Detection
read 2026-10-23 19:23 UTC- Nuclei template
- none so far ProjectDiscovery
- Exploit-DB
- no entry Exploit-DB
- Proof-of-concept repositories
- 7 repositories, unverifiedSaferman/CVE-2020-7471secoba/DjVul_StringAggSNCKER/CVE-2020-7471Tempuss/CTF_CVE-2020-7471victomteng1997/cve-2020-7471-Time_Blind_SQLi- PoC-in-GitHub
Sources
- NVDCVSS 3.19.8read 2026-10-23
- NVDCVSS 2.07.5read 2026-10-23
- NVDweakness (CWE)CWE-89read 2026-10-23
- FIRST EPSSEPSS score65.6 %read 2026-10-23
- PoC-in-GitHubproof of concept7read 2026-10-23
- OSVaffected packages—
Technical details
- CVSS v3 Vector
- CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
- Published
- 2020-02-03
- Last Modified
- 2026-06-17
- NVD status
- Modified
Frequently asked questions
What is CVE-2020-7471?
Is CVE-2020-7471 actively exploited?
What is the CVSS score for CVE-2020-7471?
Running Django? Hear about its next vulnerability
Surveillance reads the versions in your stack — a domain, a lockfile or a list — checks each CVE against the ranges its sources publish, and alerts you when one you run is exploited or enters CISA KEV. A version it cannot read stays « version not verified ».
No credit card required · No monthly cap on website lookups · 250 API requests/month
Go further
- Following what attackers exploit right now? The CISA KEV additions of the month, with their patch deadlines.
- Running this software? Vulnerability monitoring alerts you to new vulnerabilities in your products.
Related vulnerabilities
Same product first, then the same vendor advisory and the same publication week.