Skip to content
Noroxi
NVD / CVE Program· CNA mitre

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 django.contrib.admindocs.

Noroxi assessment

Priority: Monitor (action score 20/100)

  • The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
  • Probability of exploitation in the next 30 days: 2.7% (FIRST EPSS); higher than 86.1% of all records.
  • Anyone who can reach it over the internet can trigger it. Administrator privileges are required. No user action is required. No special conditions are required; it is repeatable.
  • Fixed version: python-django (Debian:10) 1:1.11.29-1+deb10u11; python-django (Debian:12) 2:2.2.24-1; python-django (Debian:9) 1:1.10.7-2+deb9u14.
  • Mentioned 1 time in Turkish national cyber security advisories (siberguvenlik.gov.tr).

Low priority for now. Upgrade to python-django (Debian:10) 1:1.11.29-1+deb10u11; python-django (Debian:12) 2:2.2.24-1; python-django (Debian:9) 1:1.10.7-2+deb9u14 or later.

Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it

Primary sources: NVD · CVE.org · FIRST EPSS

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.

MediumCVSS 4.9 · v3.1—No exploit Fix available
Published
Jun 8, 2021
Updated
Jun 16, 2026
EPSS
2.7% · 86th percentile

Report tools

JSON

Action score

20

Monitor

Low priority for now.

CVSS
19 / 40 · 4.9 / 10
CISA KEV
0 / 30 · Not listed
EPSS
1 / 30 · 2.7%

Get told when this record changes

  • Not in KEV: no record of exploitation in the wild
  • No public exploit code on record
  • A fix has been released

If any of these changes, we'll tell you in the daily email digest.

Follow CVE-2021-33203

When you'll hear from us

  • when it enters CISA KEV
  • when exploit code appears or is weaponized
  • when the record is updated (including a fixed version)
  • when EPSS rises 20 points in a week

One daily email digest (06:00 UTC); connect a webhook for KEV listings and weaponized exploits instantly.

Your free account also gets you

Running WordPress? Scan your site free with WP Lens

  • Stack alerts: add the products and versions you run, get the new CVEs that affect them
  • Uptime monitoring: 1 site, instant email when it goes down
  • Add your domain: subdomains and takeover risk scanned every week (1 domain)
  • 10 scans an hour on the security tools (3 a day without an account), an API key and MCP
  • All your scans in one panel: findings, what changed in the last scan, a report per domain or per client (PDF, share link)
All free tools

Sign up with email · Have an account? Sign in

Free account, no card. Unfollow any time.

Running WordPress? Scan your site free with WP Lens

Is your version affected? Check it

Noroxi analysis

What does it mean in your environment?

The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.

We use this product, ask for help

Affected systems

Is your version affected?

Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.

VendorProduct
djangoprojectdjango
fedoraprojectfedora

Affected versions

NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.

  • djangoproject djangobefore 2.2.24
  • djangoproject django3.0.0 and later · before 3.1.12
  • djangoproject django3.2.0 and later · before 3.2.4
  • fedoraproject fedora35

Package-level exposure

OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.

EcosystemPackageAffected rangeFix
Debian:10python-djangobefore 1:1.11.29-1+deb10u111:1.11.29-1+deb10u11
Debian:12python-djangobefore 2:2.2.24-12:2.2.24-1
Debian:9python-djangobefore 1:1.10.7-2+deb9u141:1.10.7-2+deb9u14
openSUSE:Leap 15.3python-Djangobefore 2.2.28-bp153.2.3.12.2.28-bp153.2.3.1
PyPIdjangofrom 3.0 · before 3.1.123.1.12
PyPIdjangofrom 3.2 · before 3.2.43.2.4
PyPIdjangobefore 2.2.242.2.24
Red Hat:openstack:16.1::el8python-django20-bash-completionbefore 0:2.0.13-16.el8ost.10:2.0.13-16.el8ost.1
Red Hat:openstack:16.2::el8python-django20before 0:2.0.13-16.el8ost.10:2.0.13-16.el8ost.1
Red Hat:openstack:16.2::el8python3-django20before 0:2.0.13-16.el8ost.10:2.0.13-16.el8ost.1
Red Hat:satellite_capsule:6.10::el7foremanbefore 0:2.5.2.17-2.el7sat0:2.5.2.17-2.el7sat
Red Hat:satellite_capsule:6.10::el7python-aiohttpbefore 0:3.7.4-1.el7pc0:3.7.4-1.el7pc
Red Hat:satellite_capsule:6.10::el7python-ecdsabefore 0:0.13.3-2.el7pc0:0.13.3-2.el7pc
Red Hat:satellite_capsule:6.10::el7python-pyyamlbefore 0:5.4.1-1.el7pc0:5.4.1-1.el7pc
Red Hat:satellite_capsule:6.10::el7python-urllib3before 0:1.26.5-1.el7pc0:1.26.5-1.el7pc
Red Hat:satellite_capsule:6.10::el7python3-djangobefore 0:2.2.24-1.el7pc0:2.2.24-1.el7pc
Red Hat:satellite_capsule:6.10::el7python3-ecdsabefore 0:0.13.3-2.el7pc0:0.13.3-2.el7pc
Red Hat:satellite_capsule:6.10::el7python3-pyyamlbefore 0:5.4.1-1.el7pc0:5.4.1-1.el7pc
Red Hat:satellite_capsule:6.10::el7python3-urllib3before 0:1.26.5-1.el7pc0:1.26.5-1.el7pc
Red Hat:satellite_capsule:6.10::el7satellitebefore 0:6.10.0-3.el7sat0:6.10.0-3.el7sat
Red Hat:satellite_capsule:6.10::el7satellite-capsulebefore 0:6.10.0-3.el7sat0:6.10.0-3.el7sat
Red Hat:satellite_capsule:6.10::el7tfm-rubygem-nokogiribefore 0:1.11.3-2.el7sat0:1.11.3-2.el7sat
Red Hat:satellite:6.10::el7candlepinbefore 0:4.0.9-1.el7sat0:4.0.9-1.el7sat
Red Hat:satellite:6.10::el7tfm-rubygem-actionpackbefore 0:6.0.3.7-1.el7sat0:6.0.3.7-1.el7sat

+68

Other highest-scoring records for the same primary product.

  • CVE-2022-34265An issue was discovered in Django 3.2 before 3.2.14 and 4.0 before 4.0.6.
    61This week
  • CVE-2020-7471Django 1.11 before 1.11.28, 2.2 before 2.2.10, and 3.0 before 3.0.3 allows SQL Injection if untrusted data is used as a StringAgg delimiter
    59Plan
  • CVE-2019-19844Django before 1.11.27, 2.x before 2.2.9, and 3.x before 3.0.1 allows account takeover.
    55Plan

Published before and after this one in the same product

  • ← EarlierCVE-2021-28658Apr 6, 2021 · In Django 2.2 before 2.2.20, 3.0 before 3.0.14, and 3.1 before 3.1.8, MultiPartParser allowed directory traversal via uploaded files with su
    22Monitor
  • ← EarlierCVE-2021-31542May 5, 2021 · In Django 2.2 before 2.2.21, 3.1 before 3.1.9, and 3.2 before 3.2.1, MultiPartParser, UploadedFile, and FieldFile allowed directory traversa
    32Monitor
  • Later →CVE-2021-33571Jun 8, 2021 · In Django 2.2 before 2.2.24, 3.x before 3.1.12, and 3.2 before 3.2.4, URLValidator, validate_ipv4_address, and validate_ipv46_address do not
    32Monitor

Remediation

Which version to upgrade to

Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.

Product / packageFixed versionSource
debian:python-django2:2.2.24-1 · Debian:12Package registry (OSV)
opensuse:python-Django2.2.28-bp153.2.3.1 · openSUSE:Leap 15.3Package registry (OSV)
PyPI:django2.2.24Package registry (OSV)
PyPI:django3.1.12Package registry (OSV)
PyPI:django3.2.4Package registry (OSV)
red hat:candlepin0:4.0.9-1.el7sat · Red Hat:satellite:6.10::el7Package registry (OSV)
red hat:foreman0:2.5.2.17-2.el7sat · Red Hat:satellite_capsule:6.10::el7Package registry (OSV)
red hat:python-django200:2.0.13-16.el8ost.1 · Red Hat:openstack:16.2::el8Package registry (OSV)
red hat:python-ecdsa0:0.13.3-2.el7pc · Red Hat:satellite_capsule:6.10::el7Package registry (OSV)
red hat:python-pyyaml0:5.4.1-1.el7pc · Red Hat:satellite_capsule:6.10::el7Package registry (OSV)
red hat:python3-django200:2.0.13-16.el8ost.1 · Red Hat:openstack:16.2::el8Package registry (OSV)
red hat:python3-ecdsa0:0.13.3-2.el7pc · Red Hat:satellite_capsule:6.10::el7Package registry (OSV)
red hat:python3-pyyaml0:5.4.1-1.el7pc · Red Hat:satellite_capsule:6.10::el7Package registry (OSV)
red hat:satellite0:6.10.0-3.el7sat · Red Hat:satellite_capsule:6.10::el7Package registry (OSV)
red hat:satellite-capsule0:6.10.0-3.el7sat · Red Hat:satellite_capsule:6.10::el7Package registry (OSV)
red hat:tfm-rubygem-activerecord-session_store0:2.0.0-1.el7sat · Red Hat:satellite:6.10::el7Package registry (OSV)
red hat:tfm-rubygem-nokogiri0:1.11.3-2.el7sat · Red Hat:satellite_capsule:6.10::el7Package registry (OSV)
suse:ardana-cobbler8.0+git.1614096566.e8c2b27-3.44.3 · SUSE:HPE Helion OpenStack 8Package registry (OSV)
suse:cassandra3.11.10-5.3.5 · SUSE:HPE Helion OpenStack 8Package registry (OSV)
suse:crowbar-openstack4.0+git.1616146720.44daffca0-9.81.2 · SUSE:OpenStack Cloud 7Package registry (OSV)
suse:documentation-hpe-helion-openstack-installation8.20210512-1.32.5 · SUSE:HPE Helion OpenStack 8Package registry (OSV)
suse:documentation-hpe-helion-openstack-operations8.20210512-1.32.5 · SUSE:HPE Helion OpenStack 8Package registry (OSV)
suse:documentation-hpe-helion-openstack-opsconsole8.20210512-1.32.5 · SUSE:HPE Helion OpenStack 8Package registry (OSV)
suse:grafana6.7.4-1.24.2 · SUSE:OpenStack Cloud 7Package registry (OSV)
suse:kibana4.6.6-9.2 · SUSE:OpenStack Cloud 7Package registry (OSV)
suse:monasca-installer20180608_12.47-16.2 · SUSE:OpenStack Cloud 7Package registry (OSV)
suse:python-Django1.8.19-3.29.1 · SUSE:OpenStack Cloud 7Package registry (OSV)
suse:python-Django2.2.28-bp153.2.3.1 · SUSE:Package Hub 15 SP3Package registry (OSV)
suse:python-py1.8.1-11.16.2 · SUSE:OpenStack Cloud 7Package registry (OSV)
suse:rubygem-activerecord-session_store0.1.2-3.4.2 · SUSE:OpenStack Cloud 7Package registry (OSV)

Exploit status

No known public exploit

No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.

Research context

For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.

Timeline

From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.

No dated events beyond publication.

No history yet (it accumulates with the daily EPSS job).

Patch and commit links

Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.

No commit or PR link among the references.

Finders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.

No credits in the CNA record.

Variant candidates

Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.

No nightly-computed relations.

Chain candidates

An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.

—

Bug bounty scope

No known public program.

Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).

National notice (Türkiye Cybersecurity Directorate / USOM)

Official security notices citing this record; remediation advice is on the agency's page.

All national notices →

Technical details

Attack conditions

  • Anyone who can reach it over the internet can trigger it.
  • Administrator privileges are required.
  • No user action is required.
  • No special conditions are required; it is repeatable.

If successful

Confidentiality
high · data can be read
Integrity
none
Availability
none
Attack vector
Network
Attack complexity
Low
Privileges required
High
User interaction
None
Scope
Unchanged
Confidentiality impact
High
Integrity impact
None
Availability impact
None

CVSS vector

CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:N/A:N

nvd-primary

Root cause

A user-supplied file name is joined with the allowed directory, but the result is never checked to confirm it is still inside that directory.

A representative example of this vulnerability class. Not the vendor's source code; it shows the faulty pattern and its fix.

Vulnerable

ts
const file = path.join(ROOT, req.query.name);res.sendFile(file);

Fixed

ts
const file = path.resolve(ROOT, req.query.name);if (!file.startsWith(ROOT + path.sep)) {  return res.sendStatus(400);}res.sendFile(file);

Change log

  1. Fix✗ → ✓

For records you follow, these changes also arrive as notifications. →

References

All records