Loading vulnerability…
CVE-2020-7471 is a SQL injection vulnerability in Django's PostgreSQL-specific aggregation support, affecting Django 1.11 before 1.11.28, 2.2 before 2.2.10, and 3.0 before 3.0.3. The flaw exists in contrib.postgres.aggregates.StringAgg when application code passes untrusted input as the delimiter argument. A suitably crafted delimiter can break SQL escaping during query construction, allowing attacker-controlled SQL to be injected into the generated statement. This is particularly relevant in applications that expose export or reporting functionality where users can choose a column or row delimiter.
Mallory correlates every CVE against your assets, your vendors, and active adversary campaigns. Know which vulnerabilities matter for you, not just which ones are loud.
What it means. What to do now. Patch path, mitigations, and the assume-compromise checklist.
What an attacker gets, and what they’ve been doing with it.
If you can’t patch tonight, do this now.
Patch, then assume compromise.
1 valid exploit after Mallory filtered fakes, detection scripts, and README-only repos.
This repository provides a proof-of-concept (POC) environment and exploit for CVE-2020-7471, a SQL injection vulnerability in Django's StringAgg(delimiter) function when used with PostgreSQL. The main exploit script, CVE-2020-7471.py, demonstrates how an attacker can manipulate the delimiter argument to inject SQL code, potentially allowing data extraction or modification. The repository includes a minimal Django project (sqlvul_project) and a vulnerable app (vul_app) with a simple Info model. The README provides setup instructions, including installing a vulnerable Django version and configuring PostgreSQL. The exploit is operational locally and requires the attacker to execute Python code with access to the Django environment and database. No remote network endpoints are exposed by default, but the database connection details (host: 127.0.0.1, port: 5432, user: postgres, password: postgres) are fingerprintable. The exploit demonstrates the vulnerability rather than providing a weaponized or automated attack.
Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.
Vendor-confirmed product mapping. Mallory continuously reconciles this list against your asset inventory.
No public activity tracked yet. Mallory keeps watching.
No public activity observed for this vulnerability.
Query your assets running an affected version, and investigate the blast radius.
Every observed campaign linking this CVE to a named adversary.
Malware families riding this exploit, with evidence and IOCs.
YARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.
Cross-references every affected SKU, including bundled OEM variants.
Community discussion across Reddit, Mastodon, and other social sources.