CVE-2025-30391
Published: 30 April 2025
Summary
CVE-2025-30391 is a high-severity Improper Input Validation (CWE-20) vulnerability in Microsoft Dynamics 365 Customer Service. Its CVSS base score is 8.1 (High).
Operationally, ranked in the top 23.2% of CVEs by exploit likelihood; it is not currently listed in the CISA KEV catalog.
Deeper analysis
CVE-2025-30391 is an improper input validation vulnerability, tracked under CWE-20, that affects Microsoft Dynamics. Disclosed on April 30, 2025, the flaw carries a CVSS 3.1 base score of 8.1 reflecting a network attack vector, high complexity, and no requirements for authentication or user interaction, with high impact to confidentiality, integrity, and availability.
An unauthenticated attacker can exploit the issue remotely over a network to disclose information from the affected Dynamics deployment. The absence of required privileges or user interaction lowers the bar for initial access, although the high attack complexity noted in the CVSS vector indicates that successful exploitation is not trivial.
The official Microsoft Security Response Center advisory at https://msrc.microsoft.com/update-guide/vulnerability/CVE-2025-30391 supplies remediation guidance and patch availability for supported Dynamics versions. EPSS scores remain low, with a current value of 0.0095 and a recorded peak of 0.0161.
EU & UK References
- 🇪🇺 ENISA EUVD: EUVD-2025-12756
Vulnerability details
Improper input validation in Microsoft Dynamics allows an unauthorized attacker to disclose information over a network.
- CWE(s)
Related Threats
No named actor attribution yet. ATT&CK technique mapping in progress for this CVE.
Affected Assets
Mitigating Controls
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.
Security testing and developer training directly verify and enforce proper input validation, reducing exploitability of injection and malformed-data weaknesses.
Security testing and evaluation at multiple SDLC stages directly detects missing or flawed input validation, with the required remediation process ensuring fixes are applied.
Directly implements checks on information inputs to reject invalid data before processing.
Spam protection mechanisms perform filtering and detection on inbound/outbound messages, directly compensating for missing or weak input validation of unsolicited content.