CVE-2025-57833GHSA-6W2R-R2M5-XQ5WBIT-DJANGO-2025-57833PYSEC-2025-105
An issue was discovered in Django 4.2 before 4.2.24, 5.1 before 5.1.12, and 5.2 before 5.2.6.
- Published
- Last modified
- Where the record stands: published, rejected by its publisher, or superseded by another id.What do these mean? →
- published
- Whether CISA lists it in its Known Exploited Vulnerabilities catalog: proof that attackers are using it.What do these mean? →
- Not listed in CISA KEV
- Fix
- Fixed in 4.2.24, 5.1.12, 5.2.6
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- 5 proofs of concept on GitHub
CISA's decision points: whether it is exploited, whether attacks can be automated, and how much control an attacker gets. Assessed (SSVC 2.0.3).What do these mean? →
- Exploitation: poc
- Automatable: no
- Technical impact: total
Summary
An issue was discovered in Django 4.2 before 4.2.24, 5.1 before 5.1.12, and 5.2 before 5.2.6. FilteredRelation is subject to SQL injection in column aliases, using a suitably crafted dictionary, with dictionary expansion, as the **kwargs passed QuerySet.annotate() or QuerySet.alias().
Timeline
- CVE published
- CISA SSVC assessment
Exploitation: poc · Automatable: no · Technical impact: total
- Record last updated
- EPSS reached 10%
FIRST estimates at least a 10% chance of exploitation in the next 30 days
Affected versions
- djangoproject Django
From 4.2 · fixed in 4.2.24; From 5.1 · fixed in 5.1.12; From 5.2 · fixed in 5.2.6
- djangoPyPI
fixed in 4.2.24
- djangoPyPI
From 5.0a1 · fixed in 5.1.12
- djangoPyPI
From 5.2a1 · fixed in 5.2.6
- djangoPyPI
From 4.2 · fixed in 4.2.24; From 5.1 · fixed in 5.1.12; From 5.2 · fixed in 5.2.6