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.
References
Configurations
No configuration.
History
10 Jun 2025, 18:15
Type | Values Removed | Values Added |
---|---|---|
References |
|
10 Jun 2025, 17:24
Type | Values Removed | Values Added |
---|---|---|
Summary | (en) 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. | |
References |
|
05 Jun 2025, 20:12
Type | Values Removed | Values Added |
---|---|---|
Summary |
|
05 Jun 2025, 03:15
Type | Values Removed | Values Added |
---|---|---|
New CVE |
Information
Published : 2025-06-05 03:15
Updated : 2025-06-10 18:15
NVD link : CVE-2025-48432
Mitre link : CVE-2025-48432
CVE.ORG link : CVE-2025-48432
JSON object : View
Products Affected
No product.
CWE
CWE-117
Improper Output Neutralization for Logs