Raw vector
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:LSummary
CVE-2024-53675 is a high-severity aka Blind XPath Injection (CWE-91) vulnerability in Hpe Insight Remote Support. Its CVSS base score is 7.3 (High).
Operationally, exploitation aligns with the MITRE ATT&CK technique Content Injection (T1659); ranked in the top 0.3% of CVEs by exploit likelihood; it is not currently listed in the CISA KEV catalog.
The strongest mitigations our analysis identified map to CM-6 (Configuration Settings) and SA-11 (Developer Testing and Evaluation) — 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-2024-53675 is an XML external entity injection vulnerability, tracked under CWEs 91 and 611, that affects HPE Insight Remote Support. The flaw permits improper processing of untrusted XML input and is rated 7.3 on CVSS 3.1 with a vector of AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:L.
Unauthenticated remote attackers can send crafted XML payloads over the network to trigger the vulnerability, enabling limited information disclosure along with secondary effects on integrity and availability in certain configurations.
The HPE security bulletin at https://support.hpe.com/hpesc/public/docDisplay?docLocale=en_US&docId=hpesbgn04731en_us addresses mitigation steps and available patches for the affected product versions.
The associated EPSS score stands at 0.2501 with no material rise from a lower baseline.
OWASP Top 10 for Web (2025)
EU & UK References
- 🇪🇺 ENISA EUVD: EUVD-2024-52023
Vulnerability Data
An XML external entity injection (XXE) vulnerability in HPE Insight Remote Support may allow remote users to disclose information in certain cases.
- CWE(s)
Related Threats
MITRE ATT&CK Enterprise Techniques
CVEs Like This One
Affected Assets
Mitigating Controls
Control response
—
—
—
V1.5.1V15.3.2
Mitigating Controls (NIST 800-53 r5) AI
Secure configuration settings can disable external entity processing in XML parsers.
Developer testing can discover XXE flaws through targeted XML parsing tests.
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.
Hardened XML parser configurations directly disable external entity resolution.
Secure SDLC directly requires input neutralization and validation that eliminates XML injection flaws.
Vulnerability scanning can discover XXE flaws but does not prevent their introduction in code.
Patching eliminates XXE-vulnerable parser versions but is only one aspect of software maintenance.
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.
Vulnerability management identifies and patches XML libraries with unsafe default entity settings.
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.