CVE-2025-48432

django: Django Path Injection Vulnerability

Published Jun 5, 2025 CVSS 3.1 · 4 Medium EPSS < 1% KEV · Not listed
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.

Analysis

No analysis available yet

Remediation

No remediation available yet

Tracking

Sign in to view the affected projects.

Advisories

Source ID Title
Debian DLA Debian DLA DLA-4210-1 python-django security update
Debian DSA Debian DSA DSA-6136-1 python-django security update
EUVD EUVD EUVD-2025-16951 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.
Github GHSA Github GHSA GHSA-7xr5-9hcq-chf9 Django Improper Output Neutralization for Logs vulnerability
Ubuntu USN Ubuntu USN USN-7555-1 Django vulnerability
History
Type Values Removed Values Added
First Time appeared Debian
Debian debian Linux
CPEs cpe:2.3:a:djangoproject:django:*:*:*:*:*:*:*:*
cpe:2.3:o:debian:debian_linux:11.0:*:*:*:*:*:*:*
Vendors & Products Debian
Debian debian Linux
Type Values Removed Values Added
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. 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
Type Values Removed Values Added
Title django: Django Path Injection Vulnerability
References
Metrics threat_severity

None

threat_severity

Moderate

Type Values Removed Values Added
Metrics ssvc

{'options': {'Automatable': 'no', 'Exploitation': 'none', 'Technical Impact': 'partial'}, 'version': '2.0.3'}

Type Values Removed Values Added
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.
Weaknesses CWE-117
References
Metrics cvssV3_1

{'score': 4, 'vector': 'CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:C/C:N/I:L/A:N'}

Weaknesses
  • CWE-117

    Improper Output Neutralization for Logs

Sources

Status
PUBLISHED
Assigner
mitre
Published
Updated
Jun 11, 2025, 2:59 PM
Reserved
May 21, 2025, 12:00 AM
Status
Analyzed
Published
Jun 5, 2025, 3:15 AM
Modified
Jun 17, 2026, 9:29 AM
Severity
Moderate
Public date
Jun 5, 2025, 12:00 AM