Log forgery via unescaped request paths
Published Jun 5, 2025 · Updated Jun 11, 2025
Log injection in Django 4.2 before 4.2.23, 5.1 before 5.1.11, and 5.2 before 5.2.3 allows remote attackers to forge logs via URLs. Internal HTTP response logging passes request.path control characters to log formatters without safe encoding, including newlines and ANSI escape sequences. An unauthenticated request must reach a logged response path; the result is limited to altered log appearance or structure in terminals and downstream systems, not Django's security model.
Summary
What happened
Log injection in Django 4.2 before 4.2.23, 5.1 before 5.1.11, and 5.2 before 5.2.3 allows remote attackers to forge logs via URLs. Internal HTTP response logging passes request.path control characters to log formatters without safe encoding, including newlines and ANSI escape sequences. An unauthenticated request must reach a logged response path; the result is limited to altered log appearance or structure in terminals and downstream systems, not Django's security model.
The record
- CVE
- CVE-2025-48432
- Published
- Jun 5, 2025
- Updated
- Jun 11, 2025
- Vendor
- Django Software Foundation
- Product
- Django
- Classifications
- CWE-117
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Jun 5, 2025CVE publishedPublication date reported by the CVE source.
- Jun 11, 2025Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=4.2 <4.2.23
- Affected versionversion=5.1 <5.1.11
- Affected versionversion=5.2 <5.2.3
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo