CVE-2025-32873GHSA-8J24-CJRQ-GR2MBIT-DJANGO-2025-32873PYSEC-2025-37
An issue was discovered in Django 4.2 before 4.2.21, 5.1 before 5.1.9, and 5.2 before 5.2.1.
- Published
- Last modified
- Where the record stands: published, rejected by its publisher, or superseded by another id.What do these mean? →
- published
- Whether CISA lists it in its Known Exploited Vulnerabilities catalog: proof that attackers are using it.What do these mean? →
- Not listed in CISA KEV
- Fix
- Fixed in 4.2.21, 5.1.9, 5.2.1
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- 1 proof of concept on GitHub
CISA's decision points: whether it is exploited, whether attacks can be automated, and how much control an attacker gets. Assessed (SSVC 2.0.3).What do these mean? →
- Exploitation: none
- Automatable: yes
- Technical impact: partial
Summary
An issue was discovered in Django 4.2 before 4.2.21, 5.1 before 5.1.9, and 5.2 before 5.2.1. The django.utils.html.strip_tags() function is vulnerable to a potential denial-of-service (slow performance) when processing inputs containing large sequences of incomplete HTML tags. The template filter striptags is also vulnerable, because it is built on top of strip_tags().
Timeline
- CVE published
- CISA SSVC assessment
Exploitation: none · Automatable: yes · Technical impact: partial
- Record last updated
- EPSS reached 10%
FIRST estimates at least a 10% chance of exploitation in the next 30 days
Affected versions
- djangoproject Django
From 4.2 · fixed in 4.2.21; From 5.1 · fixed in 5.1.9; From 5.2 · fixed in 5.2.1
- djangoPyPI
From 4.2 · fixed in 4.2.21
- djangoPyPI
From 5.1 · fixed in 5.1.9
- djangoPyPI
From 5.2 · fixed in 5.2.1
- djangoPyPI
From 4.2 · fixed in 4.2.21; From 5.1 · fixed in 5.1.9; From 5.2 · fixed in 5.2.1