How severe is CVE-2025-48432?

CVE-2025-48432 has a CVSS 3.x base score of 4.0, rated medium severity. It is exploitable over network with high attack complexity, requires no privileges and no user interaction. Impact on confidentiality is none, integrity low, and availability none.

Is CVE-2025-48432 being actively exploited?

It is not currently listed in CISA's KEV catalog. Its EPSS exploit-prediction score is 1% (44th percentile), an estimate of the probability of exploitation in the next 30 days.

What products are affected by CVE-2025-48432?

CVE-2025-48432 primarily affects Djangoproject Django. In total, 2 product configurations (CPEs) are listed as vulnerable; see the affected-products list for the exact versions.

How do I fix CVE-2025-48432?

Review the linked vendor and NVD advisories for patched versions and mitigations, then upgrade or apply the recommended workaround.

Does CVE-2025-48432 have an EU (EUVD) identifier?

Yes. CVE-2025-48432 is tracked in the ENISA EU Vulnerability Database (EUVD) as EUVD-2025-16951.

When was CVE-2025-48432 published?

CVE-2025-48432 was published on 2025-06-05 and last updated on 2026-06-17.

CVE-2025-48432

CVE-2025-48432 is a medium-severity vulnerability in Djangoproject Django with a CVSS 3.x base score of 4.0. It is not currently listed as actively exploited by CISA, and its EPSS exploit-prediction score is low. The underlying weakness is classified as CWE-117.

Key facts

Severity: Medium (CVSS 3.x base score 4.0)
EPSS exploit prediction: 1% (44th percentile)
Actively exploited: Not listed in CISA KEV
EU (EUVD) id: EUVD-2025-16951
Weakness: CWE-117
Affected product: Djangoproject Django
Published: 2025-06-05
Last modified: 2026-06-17

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.

Frequently asked questions

What is 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. 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.
How severe is CVE-2025-48432?: CVE-2025-48432 has a CVSS 3.x base score of 4.0, rated medium severity. It is exploitable over network with high attack complexity, requires no privileges and no user interaction. Impact on confidentiality is none, integrity low, and availability none.
Is CVE-2025-48432 being actively exploited?: It is not currently listed in CISA's KEV catalog. Its EPSS exploit-prediction score is 1% (44th percentile), an estimate of the probability of exploitation in the next 30 days.
What products are affected by CVE-2025-48432?: CVE-2025-48432 primarily affects Djangoproject Django. In total, 2 product configurations (CPEs) are listed as vulnerable; see the affected-products list for the exact versions.
How do I fix CVE-2025-48432?: Review the linked vendor and NVD advisories for patched versions and mitigations, then upgrade or apply the recommended workaround.
Does CVE-2025-48432 have an EU (EUVD) identifier?: Yes. CVE-2025-48432 is tracked in the ENISA EU Vulnerability Database (EUVD) as EUVD-2025-16951.
When was CVE-2025-48432 published?: CVE-2025-48432 was published on 2025-06-05 and last updated on 2026-06-17.

References

Affected products (2)

cpe:2.3:a:djangoproject:django:*:*:*:*:*:*:*:*
cpe:2.3:o:debian:debian_linux:11.0:*:*:*:*:*:*:*

More vulnerabilities in Djangoproject Django

CVE-2014-0474 — Critical (CVSS 10.0): The (1) FilePathField, (2) GenericIPAddressField, and (3) IPAddressField model field classes in Django before 1.4.11,…
CVE-2026-4277 — Critical (CVSS 9.8): An issue was discovered in 6.0 before 6.0.4, 5.2 before 5.2.13, and 4.2 before 4.2.30. Add permissions on inline model…
CVE-2024-53908 — Critical (CVSS 9.8): An issue was discovered in Django 5.1 before 5.1.4, 5.0 before 5.0.10, and 4.2 before 4.2.17. Direct usage of the…
CVE-2023-31047 — Critical (CVSS 9.8): In Django 3.2 before 3.2.19, 4.x before 4.1.9, and 4.2 before 4.2.1, it was possible to bypass validation when using…
CVE-2022-34265 — Critical (CVSS 9.8): An issue was discovered in Django 3.2 before 3.2.14 and 4.0 before 4.0.6. The Trunc() and Extract() database functions…
CVE-2022-28347 — Critical (CVSS 9.8): A SQL injection issue was discovered in QuerySet.explain() in Django 2.2 before 2.2.28, 3.2 before 3.2.13, and 4.0…

All CVEs affecting Djangoproject Django →

Other CWE-117 (Improper Output Neutralization for Logs) vulnerabilities

CVE-2023-46322 — Critical (CVSS 9.8): iTermSessionLauncher.m in iTerm2 before 3.5.0beta12 does not sanitize ssh hostnames in URLs. The hostname's initial…
CVE-2023-46321 — Critical (CVSS 9.8): iTermSessionLauncher.m in iTerm2 before 3.5.0beta12 does not sanitize paths in x-man-page URLs. They may have shell…
CVE-2024-0095 — Critical (CVSS 9.0): NVIDIA Triton Inference Server for Linux and Windows contains a vulnerability where a user can inject forged logs and…
CVE-2024-25047 — High (CVSS 8.6): IBM Cognos Analytics 11.2.0 through 11.2.4 and 12.0.0 through 12.0.2 is vulnerable to injection attacks in application…
CVE-2025-57564 — High (CVSS 8.2): CubeAPM nightly-2025-08-01-1 allow unauthenticated attackers to inject arbitrary log entries into production systems…
CVE-2026-10745 — High (CVSS 7.9): Improper output neutralization for logs vulnerability in upKeeper Solutions upKeeper Instant Privilege Access on…

Browse all CWE-117 (Improper Output Neutralization for Logs) vulnerabilities →