DjangoFramework / library · Djangoproject
CVE-2025-59682
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedAn 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.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · high confidenceThe django.utils.archive.extract() function used by Django's startapp --template and startproject --template commands fails to properly validate archive entry paths, allowing partial directory traversal when archive files contain paths that share a common prefix with the target extraction directory.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data
DjangoFramework / library
>= 4.2.0, < 4.2.25>= 5.1, < 5.1.13>= 5.2, < 5.2.7CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- None
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Check installed Django versionRun 'python -m django --version' or execute 'import django; print(django.get_version())' in Python to determine the exact versionAffected if Version is 4.2.0 through 4.2.24, 5.1.0 through 5.1.12, or 5.2.0 through 5.2.6 (any version in the affected ranges)
-
Verify django.utils.archive module existsRun 'python -c "from django.utils import archive; print(archive.__file__)"' to confirm the vulnerable module is presentAffected if The module exists on the system and version check confirms an affected Django version
-
Confirm use of template extraction featureReview command history, scripts, or deployment logs for usage of 'django-admin startapp --template' or 'django-admin startproject --template' commands, or inspect any archive template files in useAffected if The startapp or startproject commands with --template flag were executed using an affected Django version
Environment is affected if Django version falls within 4.2.0-4.2.24, 5.1.0-5.1.12, or 5.2.0-5.2.6 AND the startapp/startproject --template feature was used with archive files
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
dbcve · scoped4.2.255.1.135.2.7
Upgrade Django to version 4.2.25, 5.1.13, or 5.2.7 or later. Avoid using untrusted archive templates with these commands until patched.
Django 4.2.25, 5.1.13, or 5.2.7 depending on your current major version
- Check your current Django version by running: python -m django --version
- For Django 4.2.x: Upgrade to 4.2.25 using: pip install Django==4.2.25
- For Django 5.1.x: Upgrade to 5.1.13 using: pip install Django==5.1.13
- For Django 5.2.x: Upgrade to 5.2.7 using: pip install Django==5.2.7
- Verify the upgrade completed successfully: python -m django --version
Generated from the published advisory — verify against the referenced sources before acting.
Fix this in Django
Scoped from the published advisory
- Consultation2.0 h
- Implementation3.0 h
- Testing3.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,800.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-59682 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2025-59682 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data