# CVE-2020-7471: SQL injection in Django

> Attackers can inject malicious SQL via crafted delimiters in Django's StringAgg aggregate, potentially reading or modifying database contents.

- **Severity:** Critical 9.8 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 3 Feb 2020
- **Updated:** 4 Aug 2024
- **Also known as:** ALPINE-CVE-2020-7471, BIT-django-2020-7471, DEBIAN-CVE-2020-7471, DSA-4629-1, GHSA-hmr4-m2h5-33qx, PYSEC-2020-35, UBUNTU-CVE-2020-7471, USN-4264-1

## What is CVE-2020-7471?

CVE-2020-7471 is a critical SQL injection vulnerability in Djangoproject Django, published on 3 Feb 2020. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official 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.

Weakness: CWE-89 (Improper Neutralization of Special Elements used in an SQL Command)

## Which versions are affected by CVE-2020-7471?

8 open source packages ship an affected version, including django and Django. It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `django` | Bitnami | From 1.11.0 | 1.11.28, 2.2.10, 3.0.3 |
| `django` | PyPI | All versions | 1.11.28 |
| `django` | PyPI | From 1.11 | 1.11.28, 2.2.10, 3.0.3 |
| `django` | PyPI | From 2.0 | 2.2.10 |
| `django` | PyPI | From 3.0 | 3.0.3 |
| `Django` | PyPI | All versions | 1.11.28 |
| `Django` | PyPI | From 2.0 | 2.2.10 |
| `Django` | PyPI | From 3.0 | 3.0.3 |

Products: Djangoproject Django.

## How do I fix CVE-2020-7471?

Upgrade django to a fixed version for your release line: 1.11.28, 2.2.10 or 3.0.3.

## Is CVE-2020-7471 being exploited?

There is no known exploitation of CVE-2020-7471 in the wild and no public exploit code.

Public exploit code:

- django 漏洞：CVE-2020-7471  Potential SQL injection via StringAgg(delimiter) 的漏洞环境和 POC (github_poc): https://github.com/Saferman/CVE-2020-7471
- Django StringAgg SQL Injection (CVE-2020-7471) (github_poc): https://github.com/secoba/DjVul_StringAgg
- CVE-2020-7471 Potential SQL injection via StringAgg(delimiter) (github_poc): https://github.com/SNCKER/CVE-2020-7471
- PoC for the SQL injection vulnerability in PostgreSQL with Django, found in Django 1.11 before 1.11.28, 2.2 before 2.2.10, and 3.0 before 3.0.3 (github_poc): https://github.com/huzaifakhan771/CVE-2020-7471-Django
- https://github.com/Tempuss/CTF_CVE-2020-7471 (github_poc): https://github.com/Tempuss/CTF_CVE-2020-7471
- https://github.com/victomteng1997/cve-2020-7471-Time_Blind_SQLi- (github_poc): https://github.com/victomteng1997/cve-2020-7471-Time_Blind_SQLi-

## Other vulnerabilities in Djangoproject Django

- [CVE-2026-4277](https://insights.sbomify.com/CVE-2026-4277/): Privilege abuse in GenericInlineModelAdmin (critical 9.8)
- [CVE-2024-53908](https://insights.sbomify.com/CVE-2024-53908/): Django SQL injection in HasKey(lhs, rhs) on Oracle (critical 9.8)
- [CVE-2024-42005](https://insights.sbomify.com/CVE-2024-42005/): Django SQL injection vulnerability (critical 9.8)
- [CVE-2023-31047](https://insights.sbomify.com/CVE-2023-31047/): Django bypasses validation when using one form field to upload multiple files (critical 9.8)
- [CVE-2022-34265](https://insights.sbomify.com/CVE-2022-34265/): Django `Trunc()` and `Extract()` database functions vulnerable to SQL Injection (critical 9.8)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2020-7471 and fix it if it is affected.

What it is: CVE-2020-7471 is a critical SQL injection vulnerability in Djangoproject Django, published on 3 Feb 2020. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2020-7471 in the wild and no public exploit code.

Affected packages and fixed versions:
- django (Bitnami): affected from 1.11.0; fixed in 1.11.28, 2.2.10, 3.0.3
- django (PyPI): affected all versions; fixed in 1.11.28
- django (PyPI): affected from 1.11; fixed in 1.11.28, 2.2.10, 3.0.3
- django (PyPI): affected from 2.0; fixed in 2.2.10
- django (PyPI): affected from 3.0; fixed in 3.0.3
- Django (PyPI): affected all versions; fixed in 1.11.28
- Django (PyPI): affected from 2.0; fixed in 2.2.10
- Django (PyPI): affected from 3.0; fixed in 3.0.3

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2020-7471/ (Markdown: https://insights.sbomify.com/CVE-2020-7471/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2020-7471
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2020-7471
- OSV: https://osv.dev/vulnerability/CVE-2020-7471

---
From sbomify Insights: https://insights.sbomify.com/CVE-2020-7471/
Summaries are generated and may contain mistakes; the official description above is the record.