An issue was discovered in Django 5.0 before 5.0.8 and 4.2 before 4.2.15.
Noroxi assessment
Priority: Monitor (action score 30/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: 1.2% (FIRST EPSS); higher than 69% of all records.
- 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.
- According to CISA the attack is automatable: targets can be found by mass scanning.
- Fixed version: python-django (Debian:13) 3:4.2.15-1; python-Django (openSUSE:Leap 15.5) 2.0.7-150000.1.27.1, 2.0.7-150000.1.30.1; python-Django (openSUSE:Tumbleweed) 5.0.8-1.1.
- Mentioned 1 time in Turkish national cyber security advisories (siberguvenlik.gov.tr).
Low priority for now. Upgrade to python-django (Debian:13) 3:4.2.15-1; python-Django (openSUSE:Leap 15.5) 2.0.7-150000.1.27.1, 2.0.7-150000.1.30.1; python-Django (openSUSE:Tumbleweed) 5.0.8-1.1 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
An issue was discovered in Django 5.0 before 5.0.8 and 4.2 before 4.2.15. The urlize() and urlizetrunc() template filters are subject to a potential denial-of-service attack via very large inputs with a specific sequence of characters.
- Published
- Aug 7, 2024
- Updated
- Jun 17, 2026
- EPSS
- 1.2% · 69th percentile
- CWE
- CWE-130
Report tools
Action score
30
Monitor
Low priority for now.
- CVSS
- 30 / 40 · 7.5 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 1.2%
CISA SSVC decision
- Exploitation
- none
- Automatable
- yes
- Technical impact
- partial
Vulnrichment: CISA's decision-tree inputs.
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.
Running WordPress? Scan your site free with WP Lens
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 helpAffected 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.
| Vendor | Product | CPE |
|---|---|---|
| djangoproject | django | cpe:2.3:a:djangoproject:django |
Affected versions
NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.
- djangoproject django4.2 and later · before 4.2.15
- djangoproject django5.0 and later · before 5.0.8
Package-level exposure
OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.
| Ecosystem | Package | Affected range | Fix |
|---|---|---|---|
| Debian:12 | python-django | all versions | — |
| Debian:13 | python-django | before 3:4.2.15-1 | 3:4.2.15-1 |
| openSUSE:Leap 15.5 | python-Django | before 2.0.7-150000.1.27.1 | 2.0.7-150000.1.27.1 |
| openSUSE:Leap 15.5 | python-Django | before 2.0.7-150000.1.30.1 | 2.0.7-150000.1.30.1 |
| openSUSE:Tumbleweed | python-Django | before 5.0.8-1.1 | 5.0.8-1.1 |
| openSUSE:Tumbleweed | python-Django4 | before 4.2.15-1.1 | 4.2.15-1.1 |
| PyPI | django | from 4.2 · before 4.2.15 | 4.2.15 |
| PyPI | django | from 5.0 · before 5.0.8 | 5.0.8 |
| Red Hat:ansible_automation_platform_developer:2.4::el8 | automation-controller | before 0:4.5.10-1.el8ap | 0:4.5.10-1.el8ap |
| Red Hat:ansible_automation_platform_developer:2.4::el8 | automation-controller-cli | before 0:4.5.10-1.el8ap | 0:4.5.10-1.el8ap |
| Red Hat:ansible_automation_platform_developer:2.4::el8 | python39-zipp | before 0:3.19.2-1.el8ap | 0:3.19.2-1.el8ap |
| Red Hat:ansible_automation_platform_developer:2.4::el9 | automation-controller | before 0:4.5.10-1.el9ap | 0:4.5.10-1.el9ap |
| Red Hat:ansible_automation_platform_developer:2.4::el9 | automation-controller-cli | before 0:4.5.10-1.el9ap | 0:4.5.10-1.el9ap |
| Red Hat:ansible_automation_platform_developer:2.4::el9 | python-zipp | before 0:3.19.2-1.el9ap | 0:3.19.2-1.el9ap |
| Red Hat:ansible_automation_platform_developer:2.4::el9 | python3-zipp | before 0:3.19.2-1.el9ap | 0:3.19.2-1.el9ap |
| Red Hat:ansible_automation_platform:2.4::el8 | automation-controller-server | before 0:4.5.10-1.el8ap | 0:4.5.10-1.el8ap |
| Red Hat:ansible_automation_platform:2.4::el8 | automation-controller-ui | before 0:4.5.10-1.el8ap | 0:4.5.10-1.el8ap |
| Red Hat:ansible_automation_platform:2.4::el8 | automation-controller-venv-tower | before 0:4.5.10-1.el8ap | 0:4.5.10-1.el8ap |
| Red Hat:ansible_automation_platform:2.4::el8 | python39-django | before 0:4.2.15-1.el8ap | 0:4.2.15-1.el8ap |
| Red Hat:ansible_automation_platform:2.4::el8 | python39-grpcio | before 0:1.58.3-1.el8ap | 0:1.58.3-1.el8ap |
| Red Hat:ansible_automation_platform:2.4::el8 | python39-grpcio-debuginfo | before 0:1.58.3-1.el8ap | 0:1.58.3-1.el8ap |
| Red Hat:ansible_automation_platform:2.4::el8 | python3x-django | before 0:4.2.15-1.el8ap | 0:4.2.15-1.el8ap |
| Red Hat:ansible_automation_platform:2.4::el8 | python3x-grpcio | before 0:1.58.3-1.el8ap | 0:1.58.3-1.el8ap |
| Red Hat:ansible_automation_platform:2.4::el8 | python3x-grpcio-debugsource | before 0:1.58.3-1.el8ap | 0:1.58.3-1.el8ap |
+35
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 |
|---|---|---|
| debian:python-django | 3:4.2.15-1 · Debian:13 | Package registry (OSV) |
| opensuse:python-Django | 4.2.11-150600.3.6.1 · openSUSE:Leap 15.6 | Package registry (OSV) |
| opensuse:python-Django4 | 4.2.15-1.1 · openSUSE:Tumbleweed | Package registry (OSV) |
| PyPI:django | 4.2.15 | Package registry (OSV) |
| PyPI:django | 5.0.8 | Package registry (OSV) |
| red hat:automation-controller-venv-tower | 0:4.5.10-1.el8ap · Red Hat:ansible_automation_platform:2.4::el8 | Package registry (OSV) |
| red hat:python-grpcio | 0:1.58.3-1.el9ap · Red Hat:ansible_automation_platform:2.4::el9 | Package registry (OSV) |
| red hat:python-grpcio-debugsource | 0:1.58.3-1.el9ap · Red Hat:ansible_automation_platform:2.4::el9 | Package registry (OSV) |
| red hat:python-zipp | 0:3.19.2-1.el9ap · Red Hat:ansible_automation_platform_developer:2.4::el9 | Package registry (OSV) |
| red hat:python3-grpcio | 0:1.58.3-1.el9ap · Red Hat:ansible_automation_platform:2.4::el9 | Package registry (OSV) |
| red hat:python3-grpcio-debuginfo | 0:1.58.3-1.el9ap · Red Hat:ansible_automation_platform:2.4::el9 | Package registry (OSV) |
| red hat:python3-zipp | 0:3.19.2-1.el9ap · Red Hat:ansible_automation_platform_developer:2.4::el9 | Package registry (OSV) |
| red hat:python39-grpcio | 0:1.58.3-1.el8ap · Red Hat:ansible_automation_platform:2.4::el8 | Package registry (OSV) |
| red hat:python39-grpcio-debuginfo | 0:1.58.3-1.el8ap · Red Hat:ansible_automation_platform:2.4::el8 | Package registry (OSV) |
| red hat:python39-zipp | 0:3.19.2-1.el8ap · Red Hat:ansible_automation_platform_developer:2.4::el8 | Package registry (OSV) |
| red hat:python3x-grpcio | 0:1.58.3-1.el8ap · Red Hat:ansible_automation_platform:2.4::el8 | Package registry (OSV) |
| red hat:python3x-grpcio-debugsource | 0:1.58.3-1.el8ap · Red Hat:ansible_automation_platform:2.4::el8 | Package registry (OSV) |
| suse:python-Django | 4.2.11-150600.3.6.1 · SUSE:Linux Enterprise Module for Package Hub 15 SP6 | 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.
- CVE-2024-3961428 days apartAn issue was discovered in Django 5.0 before 5.0.7 and 4.2 before 4.2.14.39Monitor
- CVE-2024-3887528 days apartAn issue was discovered in Django 4.2 before 4.2.14 and 5.0 before 5.0.7.30Monitor
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.
- TR-24-1176 · Aug 8, 2024(Django Güvenlik Bildirimi)
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
- none
- Integrity
- none
- Availability
- high · the service can be disrupted
- Attack vector
- Network
- Attack complexity
- Low
- Privileges required
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality impact
- None
- Integrity impact
- None
- Availability impact
- High
Weakness class (CWE)
CWE-130 · Improper Handling of Length Parameter InconsistencyCVSS vector
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
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)
ATT&CK techniques
—
Change log
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
Show all references (3 more)Show less
Vendor advisories and official records. Exploit/PoC links are deliberately left out.