An issue was discovered in Django 2.2 before 2.2.16, 3.0 before 3.0.10, and 3.1 before 3.1.1 (when Python 3.7+ is used).
An issue was discovered in Django 2.2 before 2.2.16, 3.0 before 3.0.10, and 3.1 before 3.1.1 (when Python 3.7+ is used). FILE_UPLOAD_DIRECTORY_PERMISSIONS mode was not applied to intermediate-level directories created in the process of uploading files. It was also not applied to intermediate-level collected static directories when using the collectstatic management command.
- Published
- Sep 1, 2020
- Updated
- Jun 16, 2026
- EPSS
- 4.0% · 90th percentile
- CWE
- CWE-276
Sign in to follow · You’ll be notified if a followed record enters KEV, gets an exploit or is updated.
Report tools
Action score
31
Monitor
Low priority for now.
- CVSS
- 30 / 40 · 7.5 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 1 / 30 · 4.0%
Noroxi analysis
No Noroxi analysis for this record yet
We don't hand-write analysis for the hundreds of thousands of vulnerabilities in the database; that wouldn't be honest. For notable, high-impact vulnerabilities our team writes the mechanism, detection and remediation steps.
We use this product, ask for helpAffected systems
| Vendor | Product | CPE |
|---|---|---|
| djangoproject | django | cpe:2.3:a:djangoproject:django |
| canonical | ubuntu linux | cpe:2.3:o:canonical:ubuntu_linux |
| fedoraproject | fedora | cpe:2.3:o:fedoraproject:fedora |
| oracle | zfs storage appliance kit | cpe:2.3:a:oracle:zfs_storage_appliance_kit |
Affected versions
NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.
- canonical ubuntu linux20.04
- djangoproject django2.2 and later · before 2.2.16
- djangoproject django3.0 and later · before 3.0.10
- djangoproject django3.1 and later · before 3.1.1
- fedoraproject fedora31
- fedoraproject fedora32
- fedoraproject fedora33
- oracle zfs storage appliance kit8.8
Package-level exposure
OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.
| Ecosystem | Package | Affected range | Fix |
|---|---|---|---|
| Alpine:v3.10 | py-django | before 1.11.29-r1 | 1.11.29-r1 |
| Alpine:v3.11 | py3-django | before 1.11.29-r1 | 1.11.29-r1 |
| Debian:10 | python-django | before 1:1.11.29-1+deb10u2 | 1:1.11.29-1+deb10u2 |
| Debian:12 | python-django | before 2:2.2.16-1 | 2:2.2.16-1 |
| PyPI | django | from 2.2 · before 2.2.16 | 2.2.16 |
| PyPI | django | from 2.2a1 · before 2.2.16 | 2.2.16 |
| PyPI | django | from 3.0 · before 3.0.10 | 3.0.10 |
| PyPI | django | from 3.0a1 · before 3.0.10 | 3.0.10 |
| PyPI | django | from 3.1 · before 3.1.1 | 3.1.1 |
| PyPI | django | from 3.1a1 · before 3.1.1 | 3.1.1 |
Same product
djangoproject: all recordsOther 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
- CVE-2019-14234An issue was discovered in Django 1.11.x before 1.11.23, 2.1.x before 2.1.11, and 2.2.x before 2.2.4.53Plan
- CVE-2021-35042Django 3.1.x before 3.1.13 and 3.2.x before 3.2.5 allows QuerySet.order_by SQL injection if order_by is untrusted input from a client of a w52Plan
- CVE-2023-24580An issue was discovered in the Multipart Request Parser in Django 3.2 before 3.2.18, 4.0 before 4.0.10, and 4.1 before 4.1.7.49Plan
Remediation
Which version to upgrade to
Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.
| Product / package | Fixed version | Source |
|---|---|---|
| alpine:py-django | 1.11.29-r1 · Alpine:v3.10 | Package registry (OSV) |
| alpine:py3-django | 1.11.29-r1 · Alpine:v3.11 | Package registry (OSV) |
| debian:python-django | 2:2.2.16-1 · Debian:12 | Package registry (OSV) |
| PyPI:django | 2.2.16 | Package registry (OSV) |
| PyPI:django | 3.0.10 | Package registry (OSV) |
| PyPI:django | 3.1.1 | Package 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.
FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).
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.
Credits
All researchersFinders, 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).
Technical details
Attack conditions
- Anyone who can reach it over the internet can trigger it.
- No account or password is 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
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality impact
- High
- Integrity impact
- None
- Availability impact
- None
Weakness class (CWE)
CWE-276 · Incorrect Default PermissionsCVSS vector
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N
nvd-primary
Attack context
MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.
Attack patterns (CAPEC)
Change log
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
- docs.djangoproject.com/en/dev/releases/security/
- groups.google.com/forum/#%21topic/django-announce/Gdqn58RqIDM
- groups.google.com/forum/#%21topic/django-announce/zFCMdgUnutU
- lists.fedoraproject.org/archives/list/package-announce%40lists.fedoraproject.org/message/F2ZHO3GZCJMP3DDTXCNVFV6ED3W64NAU/
- lists.fedoraproject.org/archives/list/package-announce%40lists.fedoraproject.org/message/OLGFFLMF3X6USMJD7V5F5P4K2WVUTO3T/
- lists.fedoraproject.org/archives/list/package-announce%40lists.fedoraproject.org/message/ZCRPQCBTV3RZHKVZ6K6QOAANPRZQD3GI/
- security.netapp.com/advisory/ntap-20200918-0004/
- usn.ubuntu.com/4479-1/
- www.djangoproject.com/weblog/2020/sep/01/security-releases/
- www.openwall.com/lists/oss-security/2020/09/01/2
- www.oracle.com/security-alerts/cpujan2021.html
Vendor advisories and official records. Exploit/PoC links are deliberately left out.