CVE-2025-59682GHSA-Q95W-C7QG-HRFFBIT-DJANGO-2025-59682PYSEC-2026-1296
An issue was discovered in Django 4.2 before 4.2.25, 5.1 before 5.1.13, and 5.2 before 5.2.7.
- 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.25, 5.1.13, 5.2.7
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or 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: none
- Automatable: no
- Technical impact: partial
Summary
An issue was discovered in Django 4.2 before 4.2.25, 5.1 before 5.1.13, and 5.2 before 5.2.7. The django.utils.archive.extract() function, used by the "startapp --template" and "startproject --template" commands, allows partial directory traversal via an archive with file paths sharing a common prefix with the target directory.
Timeline
- CVE published
- CISA SSVC assessment
Exploitation: none · Automatable: no · Technical impact: partial
- Record last updated
Affected versions
- djangoproject Django
From 4.2 · fixed in 4.2.25; From 5.1 · fixed in 5.1.13; From 5.2 · fixed in 5.2.7
- djangoPyPI
From 4.2 · fixed in 4.2.25
- djangoPyPI
From 5.1 · fixed in 5.1.13
- djangoPyPI
From 5.2 · fixed in 5.2.7
- djangoPyPI
From 4.2 · fixed in 4.2.25; From 5.1 · fixed in 5.1.13; From 5.2 · fixed in 5.2.7