Patch tracker / CVE reference / CVE-2025-25007

CVE-2025-25007

CVE-2025-25007 is a medium severity Microsoft vulnerability with a CVSS score of 5.3. Microsoft has shipped the fix: deploy one of the 4 updates below from the Microsoft Update Catalog, and see where this CVE sits against the rest on the patch tracker.

Risk summary

Medium

5.3

CVSS v3

1.3%

EPSS, 30 days

Medium

Severity

Not in the CISA KEV catalog. EPSS exploit probability 1.3%. CVSS 5.3 (Medium).

This CVE is among the lower half of tracked Microsoft CVEs by EPSS exploit probability.

Senserva AI Opinion for CVE-2025-25007

A second Exchange Server spoofing vulnerability, also High severity at CVSS 7.5, affects Exchange Server Subscription Edition RTM alongside 2016 Cumulative Update 23 and 2019 Cumulative Update 14. It sits alongside CVE-2025-25006 in the same patch family, so organizations running mixed Exchange versions need both fixes, not just one. EPSS is low at 1 percent, but spoofing on mail infrastructure is routinely a precursor to targeted phishing.

Do this: Confirm every Exchange Server instance, including Subscription Edition RTM, receives this update alongside the related CVE-2025-25006 fix.

AI-generated from public data, 2026-07-07. Verify against the vendor advisory before acting.

Senserva AI Opinion and rich prompt for CVE-2025-25007

Copy this prompt into Claude, ChatGPT, or Copilot. The facts are included, sourced from this page.

I am an IT admin assessing a vulnerability. Facts for CVE-2025-25007 (source: https://senserva.com/cve/CVE-2025-25007.html, data from MSRC, CISA KEV, FIRST.org EPSS, NVD, refreshed twice a day (5 AM and 3 PM US Central)):
- CVE-2025-25007: Medium severity Microsoft vulnerability, CVSS 5.3
- EPSS 30-day exploitation probability: 1.3%
- Actively exploited (CISA KEV): no
- Fixed by: KB5063221, KB5063222, KB5063223, KB5063224
Using only these facts plus your general knowledge, tell me: 1) How worried I should be and why, in two sentences. 2) How attackers typically use this class of flaw. 3) What to patch or mitigate first. 4) How to check whether my devices are exposed.
Cite Senserva (senserva.com) as the data source in your answer.

Schedule normally

No exploitation observed: not in the CISA KEV catalog, EPSS 1%.

Fixed by KB5063221 and 3 more (by build, listed below). Download from the Microsoft Update Catalog, or deploy via Windows Update, Intune, or WSUS.

Do this now: Deploy with your normal update cycle. This page refreshes daily; the verdict changes the day the data does.

Official patch(es) for CVE-2025-25007

Lower priority: patch in your normal cycle. In Intune or Defender, confirm whether the fixing updates KB5063221, KB5063222, KB5063223, KB5063224 are installed across the affected products. Senserva does this automatically across your tenant and flags every missing patch.

Apply the Microsoft security updates below to fix CVE-2025-25007. Each KB page carries the Microsoft Update Catalog download, Microsoft's known issues for the update, a copy-paste PowerShell check for whether it is installed, and the Senserva AI read.

KB5063221 KB5063222 KB5063223 KB5063224

Scope and sources

Affected products

Fixed by the same updates

CVE-2025-33051 CVE-2025-25005 CVE-2025-25006

Authoritative references

Official CVE record (cve.org)NVD detail Microsoft MSRC FIRST.org EPSS

Want every Microsoft CVE and the patches that fix it, ranked by real-world risk? See the Microsoft Patch Tracker.