IRONSMITHINTEL
HIGHCVSS8.8
|
Actively Exploited
|CISA KEV|CVE-2025-49704|Auth: low — authenticated user|Reboot: required|Manual only

KB5002741: Windows Server Security Update (July 2025)

Microsoft SharePoint contains a code injection vulnerability that could allow an authorized attacker to execute code over a network. This vulnerability could be chained with CVE-2025-49706. CVE-2025-53770 is a patch bypass for CVE-2025-49704, and the updates for CVE-2025-53770 include more robust protection than those for CVE-2025-49704.

Published Jul 8, 2025 · Updated May 16, 2026
Why patchRisk explained in plain English
Worst-case scenarioIf unpatched

A remote attacker, with a low-privilege account, can achieve full data confidentiality loss, arbitrary modification of data, complete denial of service or system unavailability. CISA has confirmed use of this vulnerability in known ransomware campaigns — treat as high priority for remediation. Federal agencies are required to remediate by 2025-07-23 under CISA BOD 22-01.

How the attack worksNo clicks needed

This is a Code Injection (CWE-94) vulnerability in Microsoft SharePoint. Improper control of generation of code ('code injection') in Microsoft Office SharePoint allows an authorized attacker to execute code over a network. Exploitation requires remote network access, low attack complexity, a low-privilege authenticated account, and no user interaction required.

Am I affected?Quick check

Probably yes if any of these apply:

SharePoint Administrators
IT Security
Running sharepoint server: 2016, 2019
Fixed inKB5002741, KB5002744 (applies to 2 product versions) — build 16.0.10417.20027, 16.0.5508.1000
Real-world incidentsWhat we've seen

CISA confirms this CVE has been used in known ransomware campaigns. Added to the KEV catalog on 2025-07-22; federal agencies required to remediate by 2025-07-23.

How to patch

Manual download

For air-gapped servers or out-of-band deployment. Microsoft Update Catalog returns every OS-version variant of this update.

↗ Microsoft Update CatalogKB5002741

Manual remediation steps

Apply the Microsoft Security Update

Microsoft has released an official security update that fixes this vulnerability.

Required KB Updates

    1
    KB5002741 — https://support.microsoft.com/help/5002741
    1
    KB5002744 — https://support.microsoft.com/help/5002744

Supersedes: KB5002729, KB5002732

Affected Products

    1
    Microsoft SharePoint Enterprise Server 2016
    1
    Microsoft SharePoint Server 2019

Fixed Build Numbers

    1
    16.0.10417.20027
    1
    16.0.5508.1000

Installation Methods

Windows Update (recommended)

1
Settings → Windows Update → Check for updates
2
The security update is offered if your system is in scope
3
Restart when prompted (may or may not be required for this update)

Microsoft Update Catalog (manual download)

1
Open https://catalog.update.microsoft.com
2
Search for KB5002741
3
Download the package matching your OS architecture and Windows build
4
Run the .msu installer with administrator privileges
5
Restart when prompted

WSUS / SCCM / Intune

Approve KB5002741 for the affected products in your update management console.

Microsoft Download Center Links

    1
    https://www.microsoft.com/en-us/download/details.aspx?id=108257
    1
    https://www.microsoft.com/en-us/download/details.aspx?id=108259

Verification

Confirm the update is installed:

Get-HotFix | Where-Object { $_.HotFixID -in @('KB5002741','KB5002744') }

References

    1
    Microsoft Security Response Center: https://www.microsoft.com/en-us/security/blog/2025/07/22/disrupting-active-exploitation-of-on-premises-sharepoint-vulnerabilities/
    1
    KB article: https://support.microsoft.com/help/5002741
    1
    KB article: https://support.microsoft.com/help/5002744
    1
    NVD entry: https://nvd.nist.gov/vuln/detail/CVE-2025-49704
    1
    CISA KEV: https://www.cisa.gov/known-exploited-vulnerabilities-catalog?field_cve=CVE-2025-49704

Discovery Credit

Viettel Cyber Security working with Trend Zero Day Initiative

PowerShell automationComing soon

No tested PowerShell script for this entry yet. We’re prioritising automation based on user demand.