Affected versions
Version ranges need review.
PyPIdjango
- Affected versions
- < 4.2.22
- Fixed version
- 4.2.22
PyPIdjango
- Affected versions
- >=5.2 <5.2.2 || >=5.1 <5.1.10 || >=4.2 <4.2.22
- Fixed version
- 4.2.22 · 5.1.10 · 5.2.2
PyPIdjango
- Affected versions
- >= 5.0a1, < 5.1.10
- Fixed version
- 5.1.10
PyPIdjango
- Affected versions
- >= 5.2, < 5.2.2
- Fixed version
- 5.2.2
- Affected versions
- Unknown
- Fixed version
- Not reported
- Affected versions
- Unknown
- Fixed version
- Not reported
- Affected versions
- Unknown
- Fixed version
- Not reported
Exploitation
Description
An issue was discovered in Django 5.2 before 5.2.2, 5.1 before 5.1.10, and 4.2 before 4.2.22. 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.
Links
- http://www.openwall.com/lists/oss-security/2025/06/04/5
- http://www.openwall.com/lists/oss-security/2025/06/10/2
- http://www.openwall.com/lists/oss-security/2025/06/10/3
- http://www.openwall.com/lists/oss-security/2025/06/10/4
- https://docs.djangoproject.com/en/dev/releases/security
- https://docs.djangoproject.com/en/dev/releases/security/
- https://github.com/advisories/GHSA-7xr5-9hcq-chf9
- https://github.com/pypa/advisory-database/tree/main/vulns/django/PYSEC-2025-47.yaml
- https://groups.google.com/g/django-announce
- https://nvd.nist.gov/vuln/detail/CVE-2025-48432
- https://www.djangoproject.com/weblog/2025/jun/04/security-releases
- https://www.djangoproject.com/weblog/2025/jun/04/security-releases/
- https://www.djangoproject.com/weblog/2025/jun/10/bugfix-releases

