Raw vector
CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:N/I:H/A:NSummary
CVE-2023-23391 is a medium-severity Relative Path Traversal (CWE-23) vulnerability in Microsoft 365 Copilot. Its CVSS base score is 5.5 (Medium).
Operationally, exploitation aligns with the MITRE ATT&CK technique Exploit Public-Facing Application (T1190); ranked at the 48th percentile by exploit likelihood (below the median); 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.
CVE-2023-23391 is a spoofing vulnerability affecting Microsoft Office for Android. It carries a CVSS 3.1 score of 5.5 with the vector AV:L/AC:L/PR:N/UI:R/S:U/C:N/I:H/A:N and is associated with CWE-23.
An attacker with local access and no privileges can exploit the flaw when a user performs a specific action, resulting in high impact to integrity while leaving confidentiality and availability unaffected.
Microsoft security advisories linked in the references describe available updates and mitigation steps. The EPSS score started low after disclosure, rose materially to a peak of 0.0762 on 2025-01-22, and has since receded to 0.0117, indicating a period of increased exploitation interest well after the original publication date.
OWASP Top 10 for Web (2025)
EU & UK References
- 🇪🇺 ENISA EUVD: EUVD-2023-27491
Vulnerability Data
Office for Android Spoofing Vulnerability
- CWE(s)
Related Threats
MITRE ATT&CK Enterprise Techniques
CVEs Like This One
Affected Assets
Mitigating Controls
Control response
—
—
—
V5.3.2
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 validation and path sanitization that prevent relative traversal.
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 path traversal via static/dynamic analysis, but does not itself implement the fix.
Secure development lifecycle mandates input validation and path-handling controls that directly prevent relative path traversal.
Application security requirements explicitly call for controls against path traversal and other injection flaws.
Secure architecture principles include directory isolation and canonicalization, reducing but not eliminating traversal risk.
Secure coding standards require neutralizing path traversal sequences, directly addressing CWE-23.
Information access restriction limits which files can be reached, mitigating impact but not preventing the traversal flaw.