Patch tracker / CVE reference / CVE-2025-47168

CVE-2025-47168

CVE-2025-47168 is a high severity Microsoft vulnerability with a CVSS score of 7.8. Its EPSS score puts the probability of exploitation in the next 30 days at 15%. Microsoft has shipped the fix: deploy one of the 5 updates below from the Microsoft Update Catalog, and see where this CVE sits against the rest on the patch tracker.

Risk summary

High

7.8

CVSS v3

15%

EPSS, 30 days

High

Severity

Not in the CISA KEV catalog. EPSS exploit probability 15%. CVSS 7.8 (High).

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

Senserva AI Opinion for CVE-2025-47168

This Microsoft Word remote code execution flaw reaches SharePoint Enterprise Server 2016 and SharePoint Server 2019 in addition to Office 2019, with a 13 percent EPSS score and CVSS 8.8, High Severity. Server-side Word parsing means a document uploaded to a SharePoint library can attack the farm without any user opening it. It is one of a pair of such bugs, and on-premises SharePoint remains a proven high-value target.

Do this: Update on-premises SharePoint farms before desktop Office, and check upload-triggered document processing jobs are current.

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

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

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-47168 (source: https://senserva.com/cve/CVE-2025-47168.html, data from MSRC, CISA KEV, FIRST.org EPSS, NVD, refreshed twice a day (5 AM and 3 PM US Central)):
- CVE-2025-47168: High severity Microsoft vulnerability, CVSS 7.8
- EPSS 30-day exploitation probability: 15%
- Actively exploited (CISA KEV): no
- Fixed by: KB5002710, KB5002727, KB5002729, KB5002731, KB5002732
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.

Patch this cycle

Not confirmed exploited yet, but the 30-day exploit probability is high (EPSS 15%).

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

Do this now: Patch in this maintenance window; do not let it slip to the next one.

Official patch(es) for CVE-2025-47168

Elevated priority: high severity or a meaningful exploitation probability, sooner if an affected product is internet-facing. In Intune or Defender, confirm whether the fixing updates KB5002710, KB5002727, KB5002729, KB5002731, KB5002732 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-47168. 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.

KB5002710 KB5002727 KB5002729 KB5002731 KB5002732

Scope and sources

Affected products

Fixed by the same updates

CVE-2025-47163 CVE-2025-47166 CVE-2025-47172 CVE-2025-47169

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.