Raw vector
CVSS:3.1/AV:A/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:NSummary
CVE-2024-8010 is a low-severity Improper Restriction of XML External Entity Reference (CWE-611) vulnerability in Wso2 Api Manager. Its CVSS base score is 3.5 (Low).
Operationally, exploitation aligns with the MITRE ATT&CK technique Exploit Public-Facing Application (T1190); ranked at the 19th 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 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-8010 is an XML External Entity (XXE) vulnerability, classified under CWE-611, affecting a component in WSO2 products that accepts XML input through the publisher without disabling external entity resolution. This flaw enables malicious actors to submit crafted XML payloads exploiting unescaped external entity references. The vulnerability received a CVSS v3.1 base score of 3.5 (AV:A/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:N) and was published on 2026-04-16.
Exploitation requires an attacker with low privileges (PR:L) on an adjacent network (AV:A) and involves low complexity (AC:L) with no user interaction needed. Successful attacks allow the reading of confidential files from the product's file system or access to limited HTTP resources via GET requests directed at the vulnerable product, resulting in low-impact confidentiality loss.
The official WSO2 security advisory provides details on mitigation, available at https://security.docs.wso2.com/en/latest/security-announcements/security-advisories/2026/WSO2-2024-3581/.
OWASP Top 10 for Web (2025)
EU & UK References
- 🇪🇺 ENISA EUVD: EUVD-2024-55549
Vulnerability Data
The component accepts XML input through the publisher without disabling external entity resolution. This allows malicious actors to submit a crafted XML payload that exploits the unescaped external entity references. By leveraging this vulnerability, a malicious actor can read confidential…
more
files from the product's file system or access limited HTTP resources reachable via HTTP GET requests to the vulnerable product.
- 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 can reject or sanitize XML containing external entity references.
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 practices include input validation and safe XML parser configuration that prevent XXE.
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 in development catches XXE via static analysis and dynamic XML fuzzing.
Vulnerability management identifies and patches XML libraries with unsafe default entity settings.
Secure development life cycle mandates input validation and entity handling that directly prevents XXE.
Application security requirements explicitly call for disabling external entity processing in XML parsers.
Secure architecture principles include safe parser configuration that mitigates external entity risks.
Secure coding standards require disabling DTDs and external entities in XML processing.