CVE-2025-59249 json
Microsoft Exchange Server Elevation of Privilege Vulnerability
published last yr. modified 22d ago also EUVD-2025-34376
- cvss
- 8.8
- version 3.1, CNA
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.8%
- EPSS 0.8% chance of exploitation in 30 days, percentile 58%
- public exploits
- 0
- none known
Summary
Weak authentication in Microsoft Exchange Server allows an authorized attacker to elevate privileges over a network.
Patch / fix
- Microsoft Microsoft Exchange Server 2016 Cumulative Update 23 15.01.2507.061
- Microsoft Microsoft Exchange Server 2019 Cumulative Update 14 15.02.1544.036
- Microsoft Microsoft Exchange Server 2019 Cumulative Update 15 15.02.1748.039
- Microsoft Microsoft Exchange Server Subscription Edition RTM 15.02.2562.029
Is CVE-2025-59249 in your stack? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.
Check with FencerCISA SSVC
- Exploitation
- none
- Automatable
- no
- Technical impact
- total
- Assessed
- last yr.
Exploit prediction
0.85% chance of exploitation in the next 30 days, higher than 58% of all scored CVEs (FIRST EPSS, 2026-11-09).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| CNA | 3.1 | 8.8 | CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H/E:U/RL:O/RC:C |
| CNA | 3.1 | 8.8 | CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H |
Affected products
- Microsoft Microsoft Exchange Server 2016 Cumulative Update 23
- Microsoft Microsoft Exchange Server 2019 Cumulative Update 14
- Microsoft Microsoft Exchange Server 2019 Cumulative Update 15
- Microsoft Microsoft Exchange Server Subscription Edition RTM
Classification
- Weakness
-
- CWE-1390 Weak Authentication
- Technology feeds
References
-
msrc.microsoft.com
/update-guide/vulnerability/CVE-2025-59249
vendor-advisory, patch
Sources
- CVE List CVE-2025-59249
- NVD CVE-2025-59249
Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.