Path Traversal in Django
Published Jun 8, 2021 · Updated Oct 23, 2026 · Also known as GHSA-68w8-qjq3-2gfm, PYSEC-2021-98, BIT-django-2021-33203
Original summary
Normalized public record · Updated Oct 23, 2026
Path Traversal in Django
Publisher and source text is retained separately from QFinch interpretation.
QFinch assessment
Django before 2.2.24, 3.x before 3.1.12, and 3.2.x before 3.2.4 has a potential directory traversal via django.contrib.admindocs. Staff members could use the TemplateDetailView view to check the existence of arbitrary files. Additionally, if (and only if) the default admindocs templates have been customized by application developers to also show file contents, then not only the existence but also the file contents would have been exposed. In other words, there is directory traversal outside of the template root directories.
Evidence: public source recordsAffected products
| Affected package, product or range | Fix status |
|---|---|
| Consult the referenced vendor advisory for affected versions. | Consult source advisory |
Matching a version is only one part of assessing exposure. QFinch has not assessed your environment on this public page.
Remediation
Apply the vendor-supported fixed release or mitigation, then verify the affected component is no longer reachable.
- Confirm the affected product and reachable code path exist in your environment.
- Apply the vendor-supported patch or mitigation from the primary advisory.
- Rescan the exact deployed revision and retain verification evidence.
Evidence coverage
- SSVC priority
- LOW
- Confidence
- Not available
- Aliases
- GHSA-68w8-qjq3-2gfm, PYSEC-2021-98, BIT-django-2021-33203
Scores appear only when corresponding evidence exists. Missing data is never interpreted as zero risk.
Sources and record history
- groups.google.com ↗
- docs.djangoproject.com ↗
- www.djangoproject.com ↗
- security.netapp.com ↗
- FEDORA-2022-e7fd530688 ↗
Record history
Published Jun 8, 2021 · Last refreshed Oct 23, 2026