CVE-2025-25589
Raw vector
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:NSummary
CVE-2025-25589 is a high-severity aka Blind XPath Injection (CWE-91) vulnerability in Gitee (inferred from references). Its CVSS base score is 8.1 (High).
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.
Deeper analysis AI-assisted summary
Synthesised by an AI model from the NVD description and linked references — a reading aid, not an authoritative source.
CVE-2025-25589 is an XML external entity (XXE) injection vulnerability, mapped to CWE-91, in the /weixin/aes/XMLParse.java component of yimioa versions prior to v2024.07.04. Published on 2025-03-18T16:15:27.200, it carries a CVSS v3.1 base score of 8.1 (AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:N). The issue enables attackers to execute arbitrary code by supplying a crafted XML file to the vulnerable parser.
Attackers with low privileges can exploit this over the network with low complexity and no user interaction. Exploitation leads to high confidentiality and integrity impacts through arbitrary code execution, without affecting availability or changing scope.
The referenced advisory at https://gitee.com/r1bbit/yimioa/issues/IBI81R provides details on the issue, with mitigation achieved by upgrading to yimioa v2024.07.04 or later.
OWASP Top 10 for Web (2025)
EU & UK References
- 🇪🇺 ENISA EUVD: EUVD-2025-6695
Vulnerability Data
An XML external entity (XXE) injection vulnerability in the component /weixin/aes/XMLParse.java of yimioa before v2024.07.04 allows attackers to execute arbitrary code via supplying a crafted XML file.
- CWE(s)
Related Threats
MITRE ATT&CK Enterprise Techniques
CVEs Like This One
Affected Assets
Mitigating Controls
Mitigating Controls (NIST 800-53 r5) AI
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.
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.
Security testing catches XML injection during development but does not itself implement the fix.
Logging can record injection attempts for detection but does not prevent the weakness.
Monitoring can detect exploitation but provides no preventive control over XML handling.
Secure SDLC mandates input validation and output encoding that directly prevent XML injection.
Application security requirements explicitly call for defenses against injection flaws including XML.
Secure architecture principles reduce attack surface but do not prescribe XML-specific controls.