How severe is CVE-2020-7471?

CVE-2020-7471 has a CVSS 3.x base score of 9.8, rated critical severity. It is exploitable over network with low attack complexity, requires no privileges and no user interaction. Impact on confidentiality is high, integrity high, and availability high.

Is CVE-2020-7471 being actively exploited?

It is not currently listed in CISA's KEV catalog. Its EPSS exploit-prediction score is 65% (99th percentile), an estimate of the probability of exploitation in the next 30 days.

What products are affected by CVE-2020-7471?

CVE-2020-7471 affects Djangoproject Django. See the affected-products list for the exact vulnerable versions.

How do I fix CVE-2020-7471?

Review the linked vendor and NVD advisories for patched versions and mitigations, then upgrade or apply the recommended workaround. Given its critical severity, prioritise patching exposed systems.

When was CVE-2020-7471 published?

CVE-2020-7471 was published on 2020-02-03 and last updated on 2026-06-17.

CVE-2020-7471

CVE-2020-7471 is a critical-severity vulnerability in Djangoproject Django with a CVSS 3.x base score of 9.8. Its EPSS exploit-prediction score of 65% places it in the 99th percentile, indicating an elevated likelihood of exploitation. The underlying weakness is classified as CWE-89.

Key facts

Severity: Critical (CVSS 3.x base score 9.8)
CVSS v2: 7.5
EPSS exploit prediction: 65% (99th percentile)
Actively exploited: Not listed in CISA KEV
Weakness: CWE-89
Affected product: Djangoproject Django
Published: 2020-02-03
Last modified: 2026-06-17

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.

Frequently asked questions

What is CVE-2020-7471?: 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.
How severe is CVE-2020-7471?: CVE-2020-7471 has a CVSS 3.x base score of 9.8, rated critical severity. It is exploitable over network with low attack complexity, requires no privileges and no user interaction. Impact on confidentiality is high, integrity high, and availability high.
Is CVE-2020-7471 being actively exploited?: It is not currently listed in CISA's KEV catalog. Its EPSS exploit-prediction score is 65% (99th percentile), an estimate of the probability of exploitation in the next 30 days.
What products are affected by CVE-2020-7471?: CVE-2020-7471 affects Djangoproject Django. See the affected-products list for the exact vulnerable versions.
How do I fix CVE-2020-7471?: Review the linked vendor and NVD advisories for patched versions and mitigations, then upgrade or apply the recommended workaround. Given its critical severity, prioritise patching exposed systems.
When was CVE-2020-7471 published?: CVE-2020-7471 was published on 2020-02-03 and last updated on 2026-06-17.

References

Affected products (1)

cpe:2.3:a:djangoproject:django:*:*:*:*:*:*:*:*

More vulnerabilities in Djangoproject Django

CVE-2014-0474 — Critical (CVSS 10.0): The (1) FilePathField, (2) GenericIPAddressField, and (3) IPAddressField model field classes in Django before 1.4.11,…
CVE-2026-4277 — Critical (CVSS 9.8): An issue was discovered in 6.0 before 6.0.4, 5.2 before 5.2.13, and 4.2 before 4.2.30. Add permissions on inline model…
CVE-2024-53908 — Critical (CVSS 9.8): An issue was discovered in Django 5.1 before 5.1.4, 5.0 before 5.0.10, and 4.2 before 4.2.17. Direct usage of the…
CVE-2023-31047 — Critical (CVSS 9.8): In Django 3.2 before 3.2.19, 4.x before 4.1.9, and 4.2 before 4.2.1, it was possible to bypass validation when using…
CVE-2022-34265 — Critical (CVSS 9.8): An issue was discovered in Django 3.2 before 3.2.14 and 4.0 before 4.0.6. The Trunc() and Extract() database functions…
CVE-2022-28347 — Critical (CVSS 9.8): A SQL injection issue was discovered in QuerySet.explain() in Django 2.2 before 2.2.28, 3.2 before 3.2.13, and 4.0…

All CVEs affecting Djangoproject Django →

Other CWE-89 (SQL Injection) vulnerabilities

CVE-2026-54350 — Critical (CVSS 10.0): Budibase is an open-source low-code platform. Prior to 3.39.12, an unauthenticated visitor of any published Budibase…
CVE-2026-8054 — Critical (CVSS 10.0): Improper Neutralization of Special Elements used in an SQL Command ('SQL Injection') in the Publish Audit API endpoints…
CVE-2026-42287 — Critical (CVSS 10.0): Emlog is an open source website building system. Prior to version 2.6.11, direct SQL injection in article creation and…
CVE-2026-3325 — Critical (CVSS 10.0): SQL injection (SQLi) in MegaCMS v12.0.0, specifically in the “id_territorio” parameter of the…
CVE-2025-10878 — Critical (CVSS 10.0): A SQL injection vulnerability exists in the login functionality of Fikir Odalari AdminPando 1.0.1 before 2026-01-26.…
CVE-2025-57792 — Critical (CVSS 10.0): Explorance Blue versions prior to 8.14.9 contain a SQL injection vulnerability caused by insufficient validation of…

Browse all CWE-89 (SQL Injection) vulnerabilities →