Cyber Resilience

CVE-2025-9375

Published
01 September 2025
Modified
17 June 2026
CVSS Score v4 6.9
Click a component to see what it means
Raw vectorCVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:L/VA:N/SC:N/SI:N/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X
EPSS Score 0.0045 37th percentile
Risk Priority 41 floored blend · peak EPSS

Summary

CVE-2025-9375 is a medium-severity aka Blind XPath Injection (CWE-91) vulnerability in Python (inferred from references). Its CVSS base score is 6.9 (Medium).

Operationally, exploitation aligns with the MITRE ATT&CK technique Content Injection (T1659); ranked at the 37th percentile by exploit likelihood (below the median); it is not currently listed in the CISA KEV catalog.

The strongest mitigations our analysis identified map to SI-10 (Information Input Validation) — see the control section below for these in your framework.

OWASP Top 10 for Web (2025)

A05:2025 Injection

EU & UK References

Vulnerability Data

XML Injection vulnerability in xmltodict allows Input Data Manipulation. This issue affects xmltodict: from 0.14.2 before 0.15.1. NOTE: the scope of this CVE is disputed by the vendor on the grounds that xmltodict.unparse() delegates element-name handling to Python's xml.sax.saxutils.XMLGenerator, and…

more

that XMLGenerator should be the component performing validation.

CWE(s)
CWE-91

Related Threats

MITRE ATT&CK Enterprise Techniques

T1659 Content Injection Initial Access
Adversaries may gain access and continuously communicate with victims by injecting malicious content into systems through online network traffic.
attack.mitre.org →
T1190 Exploit Public-Facing Application Initial Access
Adversaries may attempt to exploit a weakness in an Internet-facing host or system to initially access a network.
attack.mitre.org →
Derived from this CVE’s CWE(s) via the direct CWE→ATT&CK cross-walk.

CVEs Like This One

CVE-2025-54251Shared CWE-91
CVE-2026-1554Shared CWE-91
CVE-2024-25413Shared CWE-91
CVE-2023-38207Shared CWE-91
CVE-2026-47273Shared CWE-91
CVE-2023-46214Shared CWE-91
CVE-2025-49538Shared CWE-91
CVE-2025-25589Shared CWE-91
CVE-2026-41672Shared CWE-91
CVE-2026-27693Shared CWE-91

Affected Assets

Python
—
inferred from references and description; NVD did not file a CPE for this CVE

Mitigating Controls

Mitigating Controls (NIST 800-53 r5) AI

SI-10 Information Input Validation good match

Input validation directly stops unneutralized XML metacharacters from reaching the parser.

Mitigating Controls (NIST CSF 2.0) AI

Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→CSF cross-walk (authority under review) — links open the control.

PR.PS-06 mostly match
prevents

Secure SDLC directly requires input neutralization and validation that eliminates XML injection flaws.

Mitigating Controls (ISO/IEC 27001:2022 Annex A) AI

Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→ISO cross-walk (authority under review) — links open the control.

A.8.29 Security testing in development and acceptance mostly match
finds

Security testing catches XML injection during development but does not itself implement the fix.

A.8.15 Logging partial match
finds

Logging can record injection attempts for detection but does not prevent the weakness.

A.8.16 Monitoring activities partial match
finds

Monitoring can detect exploitation but provides no preventive control over XML handling.

A.8.25 Secure development life cycle partial match
prevents

Secure SDLC mandates input validation and output encoding that directly prevent XML injection.

A.8.26 Application security requirements partial match
prevents

Application security requirements explicitly call for defenses against injection flaws including XML.

A.8.27 Secure system architecture and engineering principles partial match
prevents

Secure architecture principles reduce attack surface but do not prescribe XML-specific controls.

References