CVE-2025-47953
Microsoft Office 2016 … 2019
Raw vector
CVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:HSummary
CVE-2025-47953 is a high-severity Improper Restriction of Names for Files and Other Resources (CWE-641) vulnerability in Microsoft Office. Its CVSS base score is 8.4 (High).
Operationally, exploitation aligns with the MITRE ATT&CK technique Data from Local System (T1005); ranked at the 41th 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 SI-10 (Information Input Validation) — 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-2025-47953 is a use-after-free vulnerability in Microsoft Office that carries a CVSS 3.1 score of 8.4. The flaw is tracked under CWE-641 and permits an attacker to execute arbitrary code on an affected system.
An unauthenticated local attacker can trigger the condition without user interaction or elevated privileges, resulting in full compromise of confidentiality, integrity, and availability on the target host.
The sole reference points to the Microsoft Security Response Center advisory for CVE-2025-47953, which is the authoritative source for patch availability and mitigation guidance. The associated EPSS score has remained low, with a current value of 0.0108 and a peak of 0.0146.
EU & UK References
- 🇪🇺 ENISA EUVD: EUVD-2025-17761
Vulnerability Data
Use after free in Microsoft Office allows an unauthorized attacker to execute code locally.
- CWE(s)
Related Threats
MITRE ATT&CK Enterprise Techniques
CVEs Like This One
Affected Assets
Mitigating Controls
Mitigating Controls (NIST 800-53 r5) AI
SI-10 requires validation of inputs used to construct resource names, directly stopping malformed or dangerous names from being accepted.
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 sanitization to restrict resource names derived from untrusted data.
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 can detect improper filename handling but does not itself prevent the weakness.
Secure development life cycle mandates input validation and safe resource naming practices that directly prevent CWE-641.
Application security requirements include rules for handling untrusted input when constructing file or resource names.
Secure system architecture principles discourage unsafe resource naming but do not prescribe specific controls.
Secure coding standards explicitly require validation and sanitization of filenames derived from external input.