DjangoFramework / library · Djangoproject
CVE-2025-48432
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedAn 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.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · high confidenceDjango's internal HTTP response logging feature does not properly escape the request.path parameter before writing to logs. An attacker can craft malicious URLs containing special characters (like newline, carriage return, or terminal escape sequences) that, when logged, can inject false log entries, forge log data, or potentially manipulate terminal output when logs are viewed.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data
DjangoFramework / library
>= 4.2, < 4.2.23>= 5.1, < 5.1.11>= 5.2, < 5.2.3
Debian LinuxOperating system
= 11.0CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- None
- Integrity
- Low
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:N
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Check installed Django versionRun 'python -c "import django; print(django.get_version())"' or check your requirements.txt or dependencies file for the Django versionAffected if Version is 4.2.x where x < 23, or 5.1.x where x < 11, or 5.2.x where x < 3
-
Confirm logging is configuredInspect your Django settings.py file and look for the LOGGING configuration dictionaryAffected if LOGGING setting exists and contains handlers that write to stdout, files, or syslog
-
Check if request logging handlers existReview LOGGING['handlers'] in settings.py - look for handlers with 'request' in their name or handlers that log the django.request loggerAffected if A handler is configured to process logs from the 'django.request' logger
-
Verify request.path is being loggedExamine LOGGING['loggers']['django.request'] configuration - check if the level is set and handlers are assignedAffected if The django.request logger has a level set (DEBUG, INFO, etc.) with handlers defined and request.path values would be written to logs
You are affected if your Django version falls within the vulnerable ranges AND logging of django.request (including request.path) is enabled in your configuration.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
dbcve · scoped4.2.235.1.115.2.3
Upgrade Django to version 5.2.3, 5.1.11, or 4.2.23 or later. Alternatively, implement output encoding/escaping for request.path in custom logging configurations until the patch can be applied.
Django 4.2.23, 5.1.11, or 5.2.3 depending on your current branch (upgrade to the same major.minor with patch >= the fixed version)
- 1. Check the current Django version installed: pip show django or python -m django --version
- 2. Upgrade Django to the patched version using pip: pip install 'Django>=5.2.3' (or appropriate version for your branch)
- 3. Verify the upgrade was successful: python -m django --version
- 4. Test your application to ensure no regressions
Generated from the published advisory — verify against the referenced sources before acting.
Fix this in Django
Scoped from the published advisory
- Consultation2.0 h
- Implementation4.0 h
- Testing6.0 h
- Review / QA3.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,096.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-48432 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2025-48432 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data