dbcve.org
DjangoFramework / library · Djangoproject

CVE-2023-31047

CRITICAL · 9.8 CVSS v3.1 Published 2023-05-07
Fix available
A fix is available. Upgrade to 3.2.19 / 4.1.9 or later.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable No privileges Zero-click

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 · unedited
In Django 3.2 before 3.2.19, 4.x before 4.1.9, and 4.2 before 4.2.1, it was possible to bypass validation when using one form field to upload multiple files. This multiple upload has never been supported by forms.FileField or forms.ImageField (only the last uploaded file was validated). However, Django's "Uploading multiple files" documentation suggested otherwise.

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 confidence

Django's forms.FileField and forms.ImageField only validated the last file when multiple files were uploaded to a single field, allowing attackers to bypass file validation checks by uploading a valid file followed by a malicious file. The documentation incorrectly suggested multiple file uploads were supported.

MitigationUpgrade Django to version 3.2.19, 4.1.9, 4.2.1 or later to patch the vulnerability. Additionally, audit file upload handlers to ensure only single files are accepted per field.

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
Affected:>= 3.2, < 3.2.19>= 4.0, < 4.1.9= 4.2
FedoraOperating system
Affected:= 38

CVSS 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
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

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

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 checks

Work through these to decide whether this CVE applies to you.

  1. Check Django version installed
    Run 'django-admin --version' or check the installed django package version via 'pip show django'
    Affected if Version is 3.2.x before 3.2.19, 4.0.x through 4.1.x before 4.1.9, or exactly 4.2.0
  2. Identify forms using FileField or ImageField
    Search your codebase for 'forms.FileField' or 'forms.ImageField' in all form definition files (typically forms.py)
    Affected if Any form contains FileField or ImageField and your application accepts user file uploads
  3. Check if multiple file uploads are enabled on upload fields
    Examine your form templates and form definitions for the 'multiple' attribute on file input fields, or check if the form's widget has allow_multiple_selected set
    Affected if The HTML input element has 'multiple' attribute enabled, or the widget is configured to accept multiple files
  4. Verify file validation behavior with multiple uploads
    Test uploading multiple files to a single FileField/ImageField and confirm whether validation runs on ALL files or only the last one. Check the form's clean() method and any custom validators applied to the field
    Affected if Only the last uploaded file undergoes validation while earlier files skip validation checks

You are affected if you run a vulnerable Django version (3.2 before 3.2.19, 4.0-4.1 before 4.1.9, or 4.2.0) AND your application accepts multiple file uploads to FileField or ImageField form fields, allowing malicious files to bypass validation when uploaded after a valid file.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 · scoped
Upgrade available Upgrade to 3.2.19 / 4.1.9 or later
Fixed in 3.2.194.1.9
Interim mitigation

Upgrade Django to version 3.2.19, 4.1.9, 4.2.1 or later to patch the vulnerability. Additionally, audit file upload handlers to ensure only single files are accepted per field.

Recommended fix High confidence

Django 3.2.19+ / 4.1.9+ / 4.2.1+ (latest stable release in your minor line recommended)

  1. 1. Identify the current Django version by running `django --version` or checking your requirements file
  2. 2. For Django 3.2.x: Upgrade to 3.2.19 or later (recommended: latest 3.2.x LTS) using `pip install 'Django>=3.2.19'`
  3. 3. For Django 4.0.x or 4.1.x: Upgrade to 4.1.9 or later (recommended: latest 4.1.x) using `pip install 'Django>=4.1.9'`
  4. 4. For Django 4.2.0: Upgrade to 4.2.1 or later (recommended: latest 4.2.x) using `pip install 'Django>=4.2.1'`
  5. 5. After upgrading, verify the new version with `django --version`
  6. 6. Run your application's test suite to ensure no regressions were introduced
  7. 7. If running on Fedora 38, ensure the system Django package is also updated to the patched version via `sudo dnf update`
Caveat Django minor version upgrades typically have minimal breaking changes, but review the release notes for any deprecation warnings or behavioral changes between your current version and the target 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
  • Implementation2.0 h
  • Testing4.0 h
  • Review / QA2.0 h
10.0 hours of engineering $1,720
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,752.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2023-31047 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2023-31047 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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