CVE-2025-328735.3MediumCWE-770

CVE-2025-32873: djangoproject vulnerability

djangoproject · Django

Vendor fix available · Affected: djangoproject · Exploitation: likely to be exploited (10% or more)

Not in CyberSIXT coverage yet: no article names this CVE. This page shows the public record.

14.3%probability of exploitation in the next 30 days

96th percentile

050100

Higher than 96% of scored CVEs

5.3MediumCVSS 3.1

LowMediumHighCrit.

DescriptionCVE.org

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().

Affected products1

From the CVE record. A product or version that is not listed is unknown, not unaffected.

djangoproject · Djangofrom 4.2 before 4.2.21; from 5.1 before 5.1.9; from 5.2 before 5.2.1

On the Atlas

Every published CVE is on the CyberSIXT Atlas, grouped by weakness, vendor and month.

Open the Atlas

Exploitation: Likely to be exploited (10% or more). EPSS gives it a 10% or higher chance of exploitation in the next 30 days.
CISA KEV: Not listed
Public check: No public nuclei template
Weakness: Allocation Without Limits · Denial of Service
Vendor: djangoproject
Published: May 2025
Band: Likely to be exploited (10% or more), May 2025

CoverageNo articles yet

No CyberSIXT article names CVE-2025-32873 yet, so there is no coverage timeline, action brief or change log for it. Everything on this page comes from the public CVE record, CISA KEV, EPSS and the nuclei template index. Search the archive or see the CVEs in the news.