CVE-2025-30392
Published: 30 April 2025
Summary
CVE-2025-30392 is a critical-severity Improper Authorization (CWE-285) vulnerability in Microsoft Azure Ai Bot Service. Its CVSS base score is 9.8 (Critical).
Operationally, ranked in the top 27.2% of CVEs by exploit likelihood; it is not currently listed in the CISA KEV catalog.
Deeper analysis
The vulnerability CVE-2025-30392 is an improper authorization flaw, tracked under CWE-285, that affects the Azure Bot Framework SDK. It carries a CVSS 3.1 base score of 9.8 reflecting network attackability without authentication or user interaction and full impact on confidentiality, integrity, and availability.
An unauthenticated attacker can exploit the weakness remotely to elevate privileges, allowing unauthorized access and control over affected bot services and their connected resources.
The Microsoft Security Response Center advisory at https://msrc.microsoft.com/update-guide/vulnerability/CVE-2025-30392 supplies official mitigation guidance. The associated EPSS score rose from a low baseline to a peak of 0.0184 on 2026-03-30 before receding to the current value of 0.0071, indicating post-disclosure exploitation interest that later subsided.
EU & UK References
- 🇪🇺 ENISA EUVD: EUVD-2025-12760
Vulnerability details
Improper authorization in Azure Bot Framework SDK allows an unauthorized attacker to elevate privileges 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.
Documented procedures facilitate correct implementation and ongoing management of authorization decisions.
Periodic reviews identify and correct flaws in authorization decisions or enforcement.
The control's documentation requirement reduces improper authorization by ensuring only mission-justified actions bypass authentication.
Establishing permitted attributes and values, plus auditing changes, ensures authorization decisions are based on correctly managed policy data.
Explicitly mandates authorizing remote access types before permitting connections, directly mitigating improper authorization.
The control explicitly requires authorization of each wireless access type prior to permitting connections.
Mandating explicit authorization of mobile device connections reduces the risk of improper authorization decisions for system access.
Specifying access authorizations for each account and requiring approvals for account requests enforces proper authorization decisions.