DjangoFramework / library · Djangoproject
CVE-2024-38875
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 · uneditedAn issue was discovered in Django 4.2 before 4.2.14 and 5.0 before 5.0.7. urlize and urlizetrunc were subject to a potential denial of service attack via certain inputs with a very large number of brackets.
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 · moderate confidenceDjango's urlize and urlizetrunc template filters are vulnerable to a denial of service attack via inputs containing a very large number of brackets, causing excessive resource consumption. The vulnerability exists in Django 4.2 before 4.2.14 and 5.0 before 5.0.7.
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
>= 4.2, < 4.2.14>= 5.0, < 5.0.7CVSS 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
- None
- Integrity
- None
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/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 checksWork through these to decide whether this CVE applies to you.
-
Determine installed Django versionRun `django --version` in your environment, or check your requirements file, or inspect the version string in the Django package (django/__init__.py)Affected if The version is 4.2.x where x is less than 14, or 5.0.x where x is less than 7
-
Identify usage of urlize template filterSearch your project templates (*.html files) for occurrences of the `|urlize` filter, for example `{{ some_variable|urlize }}`Affected if The filter is present and processes user-supplied input containing URLs
-
Identify usage of urlizetrunc template filterSearch your project templates (*.html files) for occurrences of the `|urlizetrunc` filter, for example `{{ some_variable|urlizetrunc:30 }}`Affected if The filter is present and processes user-supplied input containing URLs
-
Trace input to template filtersReview the views and context data that pass variables to templates using urlize or urlizetrunc to confirm whether the input originates from user requestsAffected if User-controlled data flows through these filters without validation on input length or bracket count
You are affected if your Django version is 4.2.x before 4.2.14 or 5.0.x before 5.0.7 AND your application uses the urlize or urlizetrunc template filters on user-provided input.
Generated from the published advisory. Verify against your own configuration.
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 · scoped4.2.145.0.7
Upgrade to Django 4.2.14, 5.0.7, or later versions. As a workaround, implement input validation to limit or reject requests with excessively large bracket sequences before processing.
Django 4.2.14 or Django 5.0.7 (depending on your major version branch)
- Identify your current Django version by checking your requirements.txt, pyproject.toml, or running `python -m django --version`
- If using Django 4.2.x (version >= 4.2 and < 4.2.14), upgrade to 4.2.14 by running: pip install Django==4.2.14
- If using Django 5.0.x (version >= 5.0 and < 5.0.7), upgrade to 5.0.7 by running: pip install Django==5.0.7
- After upgrading, verify the new version is installed: python -m django --version
- Test your application to ensure the urlize and urlizetrunc template filters work correctly with your existing templates
Generated from the published advisory — verify against the referenced sources before acting.
Fix this in Django
Scoped from the published advisory
- Consultation3.0 h
- Implementation6.0 h
- Testing12.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $6,720.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-38875 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2024-38875 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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