ZDF
Sign inSign up

Vulnerabilities

Vulnerability · CVE-2025-48432

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.

Published Jun 5, 2025 · catalog updated Jun 11, 2025 · Django

Check if you run it

No confirmed exploitation is on record for CVE-2025-48432. EPSS is 0.75%. Act only if a listed version of Django is installed.

Gaps on this record

  • No vendor fix or required action is stored. Compare the linked advisory before you change production.
Severity
Medium4.0
Known exploitation
Not in CISA/VulnCheck KEV
EPSS
0.75%
Remediation
Version ranges on file
Affected products
vendor djangoproject Django 5.1 <5.1.10

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.

Are you affected?

Enter the version you run. The result uses only the ranges stored on this record.

The check returns affected, not affected, or incomplete. It does not guess a version that is missing from the record.

  • vendor djangoproject Django 5.1 <5.1.105.1 <5.1.10

How to fix CVE-2025-48432

What to do

Three questions, each answered from this record only. Confirm the vendor advisory before you patch.

Should you patch?

No confirmed exploitation is on record for CVE-2025-48432. EPSS is 0.75%. Act only if a listed version of Django is installed.

Which versions are affected?

Compare what you have installed with djangoproject Django 5.1 <5.1.10 5.1 <5.1.10. Compare the installed version with the linked vendor advisory before you change production.

What should an analyst verify?

No weakness class is stored. EPSS 0.75%. There is no CISA KEV listing. No Exploit-DB or Metasploit reference is linked. Use the source links for the original advisory.

Code

The project this record applies to. Exploit listings stay in References.

No public source repository is identified for this product.

Timeline

Detection, updates, and resolution for this record.

  1. Jun 11, 2025 · EUVD

    Updated

    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.

  2. Oct 17, 2026 · Arch Linux Security

    Detected

    CVE-2025-48432 is named on the public Arch Linux Security page.

Sources

  • Arch Linux SecurityVendor advisoryCVE-2025-48432

    CVE-2025-48432 is named on the public Arch Linux Security page.

    security.archlinux.org
  • CVE.orgVulnerability recordCVE-2025-48432

    Official CVE identifier

    cve.org
  • FIRST EPSSExploitation probabilityCVE-2025-48432

    30-day exploitation probability 0.8%

    first.org
  • EUVDVulnerability recordEUVD-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 forger

    euvd.enisa.europa.eu

References

Freshness

Last verified in this catalog Oct 18, 2026. Significant claims (KEV, EPSS, CVSS, affected ranges) come from the source rows above — open the original publisher for the authoritative advisory.