CVE-2023-36429
Microsoft Dynamics 365 9.0 – 9.0.50.03
Raw vector
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:NCVSS and EPSS are reproduced from their sources (NVD, FIRST EPSS). Risk Priority is our own derived reading, not an NVD score.
Summary
CVE-2023-36429 is a medium-severity XPath Injection (CWE-643) vulnerability in Microsoft Dynamics 365. Its CVSS base score is 6.5 (Medium).
Operationally, exploitation aligns with the MITRE ATT&CK technique Steganography (T1001.002); ranked in the top 18% 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-40394
Vulnerability Data
Microsoft Dynamics 365 (On-Premises) Information Disclosure Vulnerability
- CWE(s)
Related Threats
MITRE ATT&CK Enterprise Techniques
CVEs Like This One
Affected Assets
Mitigating Controls
Control response
—
—
—
V1.2.4V1.2.7V2.2.1V4.3.1
Likely Mitigating Controls AI
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.
Controls whether organization resources are exposed to external system spheres by permitting or prohibiting their use.
The control ensures information is not released into a security sphere where the recipient lacks matching access authorizations.
The control ensures information resources are not exposed to the incorrect (public) sphere through review and authorization.
Protects against data mining that would expose resources to unauthorized spheres by enforcing detection and controls.
Restricts information flows to ensure resources are not exposed to incorrect or unauthorized spheres.
Controlling internal connections prevents exposure of resources to unintended internal spheres.
Knowing exact processing and storage locations helps avoid exposure of resources to incorrect spheres.
The control prevents exposure of the media resource to the wrong security sphere.
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 practices directly require input neutralization and query parameterization that prevent XPath injection.
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.25 mandates secure SDLC practices including secure coding guidelines, security requirements, checkpoints, testing (code scan, penetration tests) and developer training that reach XPath injection as one of many injection flaws, but leaves a bounded remainder (e.g. incomplete rigour in outsourced development per 8.30, inconsistent application across all languages/projects, or post-SDLC changes)
Application security requirements explicitly call for defenses against injection flaws including XPath injection.
A.8.27 mandates security-by-design principles (including input distrust, data validation/sanitization, least privilege, and secure design reviews against attack patterns) that reach a slice of XPath injection prevention when applied to the relevant layer, but leaves most instances (implementation bugs in query construction) to other controls such as A.8.28 secure coding or A.8.29 testing.
Secure coding standards require proper neutralization of untrusted input in XPath expressions.
Security testing in development catches XPath injection vulnerabilities before release.
Vulnerability management processes identify and remediate XPath injection flaws discovered post-deployment.
Hardening callouts derived
DISA STIG baselines are authored against specific weaknesses. Where this CVE cites a broad weakness class, the mapping is not asserted at that abstraction (owner ruling, 2026-09-25: grade only at Base and below), so no rule is shown here rather than a rule shown against the wrong grain.