CVE-2025-484324.0MediumCWE-117

CVE-2025-48432: djangoproject vulnerability

djangoproject · Django

Vendor fix available · Affected: djangoproject · Exploitation: unlikely (under 1%)

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

0.8%probability of exploitation in the next 30 days

57th percentile

050100

Higher than 57% of scored CVEs

4.0MediumCVSS 3.1

LowMediumHighCrit.

DescriptionCVE.org

An issue was discovered in Django 5.2 before 5.2.3, 5.1 before 5.1.11, and 4.2 before 4.2.23. Internal HTTP response logging does not escape request.path, which allows remote attackers to potentially manipulate log output via crafted URLs. This may lead to log injection or forgery when logs are viewed in terminals or processed by external systems.

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.23; from 5.1 before 5.1.11; from 5.2 before 5.2.3

On the Atlas

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

Open the Atlas

Exploitation: Unlikely (under 1%). EPSS under 1%, or no score yet.
CISA KEV: Not listed
Public check: No public nuclei template
Weakness: Improper Output Neutralization for Logs · Injection and Smuggling
Vendor: djangoproject
Published: June 2025
Band: Unlikely (under 1%), June 2025

CoverageNo articles yet

No CyberSIXT article names CVE-2025-48432 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.