SQL Injection Affecting python-django package, versions <2:2.2.10-1


Severity

Recommended
0.0
critical
0
10

Snyk's Security Team recommends NVD's CVSS assessment. Learn more

Threat Intelligence

Exploit Maturity
Proof of Concept
EPSS
65.34% (100th percentile)

Do your applications use this vulnerable package?

In a few clicks we can analyze your entire application and see what components are vulnerable in your application, and suggest you quick fixes.

Test your applications
  • Snyk IDSNYK-ECHOLATEST-PYTHONDJANGO-18533312
  • published5 Aug 2026
  • disclosed3 Feb 2020

Introduced: 3 Feb 2020

CVE-2020-7471  (opens in a new tab)
CWE-89  (opens in a new tab)

How to fix?

Upgrade Echo:latest python-django to version 2:2.2.10-1 or higher.

NVD Description

Note: Versions mentioned in the description apply only to the upstream python-django package and not the python-django package as distributed by Echo. See How to fix? for Echo:latest relevant fixed versions and status.

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 Base Scores

version 3.1