CVE-2023-24922
Microsoft Dynamics 365 9.0 – 9.0.45.11
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-24922 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 27% of CVEs by exploit likelihood; it is not currently listed in the CISA KEV catalog.
Deeper analysis AI-assisted summary
Synthesised by an AI model from the NVD description and linked references — a reading aid, not an authoritative source.
Microsoft Dynamics 365 (On-Premises) contains an information disclosure vulnerability tracked as CVE-2023-24922. The flaw is associated with CWE-643 and carries a CVSS 3.1 score of 6.5 reflecting network attack vector, low complexity, low privileges required, and high impact to confidentiality with no impact to integrity or availability.
An authenticated attacker with low privileges can exploit the issue remotely without user interaction to obtain sensitive information from the affected Dynamics 365 deployment. The vulnerability affects on-premises installations of the product and does not require elevated rights or special conditions beyond network reachability.
The Microsoft Security Response Center advisory published for CVE-2023-24922 supplies official mitigation guidance and patch information. The associated EPSS score has remained flat at a peak of 0.1204 with no material upward trajectory observed after disclosure.
OWASP Top 10 for Web (2025)
EU & UK References
- 🇪🇺 ENISA EUVD: EUVD-2023-28910
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
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.