CVE-2020-7471

CRITICALNVD 9.89.8
EchelonGraph scoreLOW confidence

This critical-severity CVE scores 9.8 under NVD CVSS v3. EPSS exploit-prediction score not yet available (the EPSS model rescores nightly; freshly-published CVEs typically appear within 48 hours). GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).

Triggered by: NVD CVSS baseline
Sources: nvd
Elevated
9.8
EchelonGraph verdictPatch this weekExploitation is likely or a public exploit exists.
  • High exploitation likelihood — EPSS 65%
CISA-KEV: Not listedEPSS: 65%CVSS: 9.8Exploit: NoneExposed: 0

A fix is available — apply it.

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.

CVSS v3
9.8
EG Score
9.8(low)
EPSS
99.2%
KEV
Not listed

Published

February 3, 2020

Last Modified

November 21, 2024

Advisory Details (9)

Auto-updated Jul 3, 2026
Upstream fix merged — awaiting tagged release. Sources: github_commit.
generic

[SECURITY] [DSA 4629-1] python-django security update

https://www.debian.org/security/2020/dsa-4629
generic

NetApp Product Security

https://security.netapp.com/advisory/ntap-20200221-0006/
generic

Django: Multiple vulnerabilities (GLSA 202004-17) — Gentoo security

https://security.gentoo.org/glsa/202004-17
generic

Bugtraq: [SECURITY] [DSA 4629-1] python-django security update

https://seclists.org/bugtraq/2020/Feb/30
generic

[SECURITY] Fedora 32 Update: python-django-3.0.7-1.fc32 - package-announce - Fedora mailing-lists

https://lists.fedoraproject.org/archives/list/package-announce%40lists.fedoraproject.org/message/4A2AP4T7RKPBCLTI2NNQG3T6MINDUUMZ/
generic

Redirecting to Google Groups

https://groups.google.com/forum/#%21topic/django-announce/X45S86X5bZI
github_commit

commit eb31d8453236 (django/django)

Fix landed in django/django commit eb31d8453236 — awaiting tagged release

https://github.com/django/django/commit/eb31d845323618d688ad429479c6dda973056136
generic

Archive of security issues | Django documentation | Django

https://docs.djangoproject.com/en/3.0/releases/security/
generic

oss-security - Django 3.0.3, 2.2.10 and 1.11.28: CVE-2020-7471: Potential SQL injection via ``StringAgg(delimiter)``

http://www.openwall.com/lists/oss-security/2020/02/03/1

Patch Availability(1)

Vendor / EcosystemFixed in / PatchReleasedSource
ubuntupython3-django (1:1.11.22-1ubuntu1.2) @ eoan2026-05-23ubuntu

Patches are aggregated from vendor advisories (Red Hat, Microsoft, Cisco, GitHub) and package ecosystems (OSV, GHSA). Multiple rows for the same upstream release have been deduplicated.

Affected Packages

(1 across 1 ecosystem)
PyPI(1)
PackageVulnerable rangeFixed inDependents
django1.11 ... 3.0.2 (40 versions)3.0.3—

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

All Vendor Advisories

(1)

Every vendor that published an advisory referencing this CVE — pulled from our cve_vendor_advisories aggregation. Click any row for the vendor's original advisory page.

Data Freshness Timeline

(refreshed 6× in last 7d / 33× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

  1. 2026-07-22 14:05 UTCEPSS rescore
  2. 2026-07-21 15:22 UTCEPSS rescore
  3. 2026-07-21 15:22 UTCEPSS rescore
  4. 2026-07-20 17:04 UTCEPSS rescore
  5. 2026-07-20 17:04 UTCEPSS rescore
  6. 2026-07-18 10:02 UTCEPSS rescore
  7. 2026-07-15 16:55 UTCEPSS rescore
  8. 2026-07-15 16:55 UTCEPSS rescore
  9. 2026-07-15 01:57 UTCEPSS rescore
  10. 2026-07-13 06:10 UTCEPSS rescore
  11. 2026-07-13 06:10 UTCEPSS rescore
  12. 2026-07-12 20:38 UTCOSV refresh
  13. 2026-07-12 05:44 UTCEPSS rescore
  14. 2026-07-12 05:44 UTCEPSS rescore
  15. 2026-07-11 08:25 UTCEPSS rescore
  16. 2026-07-11 08:25 UTCEPSS rescore
  17. 2026-07-09 19:07 UTCEPSS rescore
  18. 2026-07-06 16:25 UTCEPSS rescore
  19. 2026-07-05 02:28 UTCEPSS rescore
  20. 2026-07-05 02:28 UTCEPSS rescore
  21. 2026-07-02 16:57 UTCEPSS rescore
  22. 2026-07-01 15:03 UTCEPSS rescore
  23. 2026-06-29 14:04 UTCEPSS rescore
  24. 2026-06-28 14:05 UTCEPSS rescore
  25. 2026-06-27 03:06 UTCEPSS rescore
Show 53 more
  1. 2026-06-27 03:06 UTCEPSS rescore
  2. 2026-06-25 13:48 UTCEPSS rescore
  3. 2026-06-25 13:48 UTCEPSS rescore
  4. 2026-06-24 14:03 UTCEPSS rescore
  5. 2026-06-24 14:03 UTCEPSS rescore
  6. 2026-06-24 06:29 UTCOSV refresh
  7. 2026-06-23 21:31 UTCEPSS rescore
  8. 2026-06-23 21:31 UTCEPSS rescore
  9. 2026-06-21 01:57 UTCEPSS rescore
  10. 2026-06-21 01:57 UTCEPSS rescore
  11. 2026-06-18 17:51 UTCEPSS rescore
  12. 2026-06-18 17:50 UTCEPSS rescore
  13. 2026-06-17 17:50 UTCEPSS rescore
  14. 2026-06-16 17:50 UTCEPSS rescore
  15. 2026-06-15 17:46 UTCEPSS rescore
  16. 2026-06-13 22:58 UTCEPSS rescore
  17. 2026-06-13 22:58 UTCEPSS rescore
  18. 2026-06-12 23:10 UTCEPSS rescore
  19. 2026-06-12 23:10 UTCEPSS rescore
  20. 2026-06-11 13:58 UTCEPSS rescore
  21. 2026-06-11 13:58 UTCEPSS rescore
  22. 2026-06-10 22:16 UTCEPSS rescore
  23. 2026-06-10 13:20 UTCEPSS rescore
  24. 2026-06-07 15:23 UTCEPSS rescore
  25. 2026-06-07 15:23 UTCEPSS rescore
  26. 2026-06-07 10:29 UTCOSV refresh
  27. 2026-06-06 13:46 UTCEPSS rescore
  28. 2026-06-06 13:46 UTCEPSS rescore
  29. 2026-06-06 13:46 UTCEPSS rescore
  30. 2026-06-05 22:45 UTCEPSS rescore
  31. 2026-06-05 22:45 UTCEPSS rescore
  32. 2026-06-05 06:08 UTCEPSS rescore
  33. 2026-06-05 06:08 UTCEPSS rescore
  34. 2026-06-04 13:10 UTCEPSS rescore
  35. 2026-06-04 13:10 UTCEPSS rescore
  36. 2026-06-02 20:11 UTCEPSS rescore
  37. 2026-06-02 20:11 UTCEPSS rescore
  38. 2026-06-01 13:50 UTCEPSS rescore
  39. 2026-05-31 22:29 UTCEPSS rescore
  40. 2026-05-31 22:29 UTCEPSS rescore
  41. 2026-05-31 00:15 UTCEPSS rescore
  42. 2026-05-31 00:15 UTCEPSS rescore
  43. 2026-05-29 13:42 UTCEPSS rescore
  44. 2026-05-28 13:43 UTCEPSS rescore
  45. 2026-05-28 13:43 UTCEPSS rescore
  46. 2026-05-27 13:39 UTCEPSS rescore
  47. 2026-05-27 13:39 UTCEPSS rescore
  48. 2026-05-26 13:42 UTCEPSS rescore
  49. 2026-05-26 13:42 UTCEPSS rescore
  50. 2026-05-26 07:17 UTCEPSS rescore
  51. 2026-05-26 07:17 UTCEPSS rescore
  52. 2026-05-23 03:28 UTCEG score recompute
  53. 2026-05-23 03:28 UTCVendor advisory

Publicly available exploits

(3 references)

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.

  • GitHub PoCSNCKER/CVE-2020-7471
    First seen Feb 22, 2020

    CVE-2020-7471 Potential SQL injection via StringAgg(delimiter)

    Open source ↗
  • GitHub PoCsecoba/DjVul_StringAgg
    First seen Feb 13, 2020

    Django StringAgg SQL Injection (CVE-2020-7471)

    Open source ↗
  • GitHub PoCSaferman/CVE-2020-7471
    First seen Feb 11, 2020

    django 漏洞：CVE-2020-7471 Potential SQL injection via StringAgg(delimiter) 的漏洞环境和 POC

    Open source ↗

Frequently asked(5)

What is CVE-2020-7471?
CVE-2020-7471 is a critical vulnerability published on February 3, 2020. 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…
When was CVE-2020-7471 disclosed?
CVE-2020-7471 was first published in the National Vulnerability Database on February 3, 2020, with the most recent update on November 21, 2024. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2020-7471 actively exploited?
CVE-2020-7471 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 99.2% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
What is the CVSS score of CVE-2020-7471?
CVE-2020-7471 has a CVSS v3 base score of 9.8 (NVD). The EG score is currently aggregating — additional source signals are being incorporated as they become available..
How do I remediate CVE-2020-7471?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2020-7471, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2020-7471

Explore →

Is Your Infrastructure Affected by CVE-2020-7471?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Start Free Scan →Browse All CVEs