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.
01
describes (1)
Related CVEs.
| ID | severity | exploitable | ||
|---|---|---|---|---|
| CVE-2025-48432US | medium5.3 | — | ||
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 attac… | ||||
02
references
External citations — patches, advisories, analysis.
- http://www.openwall.com/lists/oss-security/2025/06/04/5ADVISORY
- http://www.openwall.com/lists/oss-security/2025/06/10/2ADVISORY
- http://www.openwall.com/lists/oss-security/2025/06/10/3ADVISORY
- http://www.openwall.com/lists/oss-security/2025/06/10/4DISCUSSION
- https://docs.djangoproject.com/en/dev/releases/security/ADVISORY
- https://groups.google.com/g/django-announceADVISORY
- https://nvd.nist.gov/vuln/detail/CVE-2025-48432WEB
- https://www.djangoproject.com/weblog/2025/jun/04/security-releases/ADVISORY
scry
Advisories like this name the exposed products attackers go after on your perimeter. See what is exposed on your perimeter with a free passive scan.
Free scan