Raw vector
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:HCVSS and EPSS are reproduced from their sources (NVD, FIRST EPSS). EPSS, Forum of Incident Response and Security Teams (FIRST), epss.first.org. Risk Priority is our own derived reading, not an NVD score.
Summary
CVE-2023-20855 is a high-severity Improper Restriction of XML External Entity Reference (CWE-611) vulnerability in Vmware Vrealize Automation. Its CVSS base score is 8.8 (High).
Operationally, exploitation aligns with the MITRE ATT&CK technique Exploit Public-Facing Application (T1190); ranked in the top 30% of CVEs by exploit likelihood; it is not currently listed in the CISA KEV catalog.
OWASP Top 10 for Web (2025)
EU & UK References
- 🇪🇺 ENISA EUVD: EUVD-2023-25034
Vulnerability Data
VMware vRealize Orchestrator contains an XML External Entity (XXE) vulnerability. A malicious actor, with non-administrative access to vRealize Orchestrator, may be able to use specially crafted input to bypass XML parsing restrictions leading to access to sensitive information or possible…
more
escalation of privileges.
- CWE(s)
Related Threats
MITRE ATT&CK Enterprise Techniques
MITRE ATT&CK v20.0
CVEs Like This One
Affected Assets
Mitigating Controls
Control response
—
—
—
V1.5.1V15.3.2
Likely Mitigating Controls
Our mappings. Per-CVE control mapping for this CVE has not run yet; the list below is derived from the weakness types (CWEs) cited in the NVD entry.
Mitigating Controls (NIST CSF 2.0)
Our mappings, derived directly from the weakness types (CWEs) cited in the NVD entry via our CWE→CSF cross-walk — 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)
Our mappings, derived directly from the weakness types (CWEs) cited in the NVD entry via our CWE→ISO cross-walk — links open the control.
Security testing in development catches XXE via static analysis and dynamic XML fuzzing.
Training developers about secure XML parsing practices (disabling external entity resolution, using safe parser configurations) reduces some instances of XXE, but the weakness is a specific implementation defect that requires technical knowledge to avoid, and developers remain fallible; the strongest control for this weakness is A.8.29 security testing, not training.
Network segregation with egress filtering at domain gateways can block the outbound HTTP/HTTPS requests that XXE makes to external servers (one exploitation path), but it does not block local file disclosure via file:// URIs, internal-network requests, or DoS via resource consumption — the weakness remains exploitable through those paths, so only a portion of exploitation is stopped.
Secure coding standards require disabling DTDs and external entities in XML processing.
A.8.30 carries its effect through the secure-development practices its contract requires of the supplier (8.25 to 8.29), so it reduces ordinary software implementation weaknesses like XXE in delivered code the way those practices do, at `partial` -- the same reasoning the owner applied to A.8.30 vs CWE-134 (format string).
REACH: a disclosure-reach control sees only instances that carry a vendor-published flaw, so `finds` is at most `partial` (rule, 2026-10-17).