LiveActive security incident?Get immediate response
CVE Record

CVE-2021-33203: 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 dja...

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.

UnknownCVSS not scoredNot KEV-listedUpdated
Discuss exposureBack to CVEs
Glexia's TakeAutomated analysismoderate

Security readout for executives and security teams

Plain-English summary

Older Django releases could let staff users with admindocs access check whether files exist outside expected template directories. File contents were exposed only where developers customized default admindocs templates to display them. This is mainly an authenticated information-disclosure risk, not a source-confirmed public exploit campaign.

Executive priority

Handle as a near-term patching and exposure-reduction item. Escalate priority for internet-facing admin surfaces, broad staff access, or customized admindocs templates that could expose file contents.

Technical view

CVE-2021-33203 affects Django before 2.2.24, 3.x before 3.1.12, and 3.2.x before 3.2.4. The issue is directory traversal in django.contrib.admindocs TemplateDetailView, enabling arbitrary file existence checks outside template roots. Content disclosure depends on custom admindocs templates showing file contents.

Likely exposure

Exposure is likely limited to Django applications running affected versions with django.contrib.admindocs enabled and reachable by staff users. Risk increases if admindocs templates were customized to reveal template file contents.

Exploitation context

The source bundle marks KEV as false and provides no cited evidence of active exploitation. Available sources describe the vulnerability and security releases, not public exploitation or weaponized use.

Researcher notes

The key constraints are staff-level access and admindocs enablement. Sources do not provide CVSS, CPE coverage, or exploitation evidence. Treat file-content exposure as conditional on local template customization, not the default behavior.

Mitigation direction

  • Upgrade Django to 2.2.24, 3.1.12, 3.2.4, or later supported releases.
  • Disable django.contrib.admindocs where it is not operationally required.
  • Restrict staff access to admin and admindocs routes.
  • Review customized admindocs templates for file-content exposure behavior.
  • Check vendor distribution advisories for packaged Django updates.

Validation and detection

  • Inventory applications using Django and record exact framework versions.
  • Confirm whether django.contrib.admindocs is installed and routed.
  • Review staff-accessible admin documentation paths and access controls.
  • Inspect customized admindocs templates for content-rendering changes.
  • Verify patched Django versions are deployed in production.
Prepared
Confidence
high
Sources
6

Public sources used

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

description · low confidence lookup

File access behavior lookup

The CVE wording references file access or upload behavior, so file telemetry and web shell review may help. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.

Open ATT&CK lookup
cve · low confidence lookup

CVE-2021-33203 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
Unknown
CVSS
Not scored
Known Exploited
No
Published
Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

0CVSS vectors
0Timeline events
0ADP providers
6Source links

CVSS and timeline data

No CVSS vectors or timeline events were available in the normalized CVE source material.

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
n/an/an/aListed
Weakness

CWE details

No CWE listed

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.