CVE-2025-48432

Description

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.

Category

4.0
CVSS
Severity: Medium
CVSS 3.1 •
EPSS 0.04%
Affected: djangoproject Django
Published at:
Updated at:

References

Frequently Asked Questions

What is the severity of CVE-2025-48432?
CVE-2025-48432 has been scored as a medium severity vulnerability.
How to fix CVE-2025-48432?
To fix CVE-2025-48432, make sure you are using an up-to-date version of the affected component(s) by checking the vendor release notes. As for now, there are no other specific guidelines available.
Is CVE-2025-48432 being actively exploited in the wild?
As for now, there are no information to confirm that CVE-2025-48432 is being actively exploited. According to its EPSS score, there is a ~0% probability that this vulnerability will be exploited by malicious actors in the next 30 days.
What software or system is affected by CVE-2025-48432?
CVE-2025-48432 affects djangoproject Django.
This platform uses data from the NIST NVD, MITRE CVE, MITRE CWE, First.org and CISA KEV but is not endorsed or certified by these entities. CVE is a registred trademark of the MITRE Corporation and the authoritative source of CVE content is MITRE's CVE web site. CWE is a registred trademark of the MITRE Corporation and the authoritative source of CWE content is MITRE's CWE web site.
© 2025 Under My Watch. All Rights Reserved.