Skip to main content
Meet us at Black Hat USA 2026— Las Vegas, August 1–6Book a Meeting
Mallory
HighCISA KEVExploited in the wildPublic exploit

Microsoft SharePoint Server remote code execution (ToolShell component)

IdentifiersCVE-2025-49704CWE-94· Improper Control of Generation of…

CVE-2025-49704 is a Microsoft Office SharePoint / SharePoint Server remote code execution vulnerability described by Microsoft as improper control of generation of code (code injection). Supporting reporting indicates the flaw was exploited as part of the ToolShell exploit chain together with CVE-2025-49706 against on-premises SharePoint Server deployments. Multiple sources in the provided content further characterize the vulnerable path as involving attacker-supplied data to the SharePoint ToolPane endpoint (/_layouts/15/ToolPane.aspx), where crafted WebPart/XML content in parameters such as MSOtlPn_DWP could reach unsafe processing paths. Kaspersky’s analysis states the exploit abused the ExcelDataSet control in Microsoft.PerformancePoint.Scorecards.Client.dll, with attacker-controlled CompressedDataTable data flowing through GetObjectFromCompressedBase64String and BinarySerialization.Deserialize, ultimately enabling arbitrary method execution via unsafe XML/deserialization behavior. Microsoft’s initial July 2025 fix was later found incomplete in some scenarios, and subsequent comprehensive fixes were issued under related CVEs in the ToolShell chain.

Share:
For your environment

Are you exposed to this one?

Mallory correlates every CVE against your assets, your vendors, and active adversary campaigns. Know which vulnerabilities matter for you, not just which ones are loud.

ANALYST BRIEF

Impact, mitigation & remediation

What it means. What to do now. Patch path, mitigations, and the assume-compromise checklist.

Impact

What an attacker gets, and what they’ve been doing with it.

Successful exploitation allows remote code execution on vulnerable on-premises SharePoint servers. In observed intrusions, attackers used this access to deploy ASPX web shells, execute commands in the IIS worker process context, steal SharePoint ASP.NET MachineKey material, establish persistence, dump credentials, move laterally, exfiltrate data, and in some cases deploy ransomware such as Warlock. Because SharePoint is commonly integrated with broader enterprise identity and collaboration infrastructure, compromise can provide a high-value foothold into the internal environment.

Mitigation

If you can’t patch tonight, do this now.

If immediate patching is not possible, reduce or remove internet exposure of on-premises SharePoint servers, especially public-facing instances. Enable and properly configure AMSI in Full Mode with Defender/endpoint protections as recommended in the reporting. Hunt for POST requests to /_layouts/15/ToolPane.aspx, unexpected ASPX files such as spinstall0.aspx in SharePoint layouts paths, suspicious w3wp.exe child processes, machine-key access, and other ToolShell-related indicators. Audit privileged accounts, remote access tooling, scheduled tasks, IIS modifications, and lateral movement activity. Assume compromise for exposed vulnerable systems during the active exploitation window until proven otherwise.

Remediation

Patch, then assume compromise.

Apply Microsoft’s security updates for affected on-premises SharePoint Server versions, including the later comprehensive updates that address the ToolShell-related bypasses and incomplete earlier fixes. The content indicates Microsoft released updates for SharePoint Subscription Edition, SharePoint Server 2019, and SharePoint Server 2016, and later updates also addressed related CVE-2025-53770 and CVE-2025-53771. Where the original July 2025 update for CVE-2025-49704 had been applied, administrators also needed to ensure the SharePoint configuration upgrade step was completed; later fixes removed that dependency. After patching, rotate SharePoint ASP.NET machine keys, restart IIS, and investigate for compromise because patching alone may not remove persistence already established by attackers.
PUBLIC EXPLOITS

Exploits

No valid public exploits. Mallory filtered out 1 candidate as fakes, detection scripts, or README-only repos.

VALID 0 / 1 TOTALView more in app

All candidate exploits were filtered out by Mallory's validation.

EXPOSURE SURFACE

Affected products & vendors

Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.

VendorProductType
Microsoft CorporationSharepoint Serverapplication
Microsoft CorporationSharepoint Server 2016application
Microsoft CorporationSharepoint Server 2019application

Vendor-confirmed product mapping. Mallory continuously reconciles this list against your asset inventory.

What this page doesn’t show

The version that knows your environment.

This page is what’s public. Mallory adds the parts that aren’t: which of your assets are affected, which adversaries are exploiting it right now, which detections to deploy, and what to do tonight.
Exposure mapping

Query your assets running an affected version, and investigate the blast radius.

Threat actor evidence28

Every observed campaign linking this CVE to a named adversary.

Associated malware27

Malware families riding this exploit, with evidence and IOCs.

Detection signatures1

YARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.

Vendor-by-vendor mapping

Cross-references every affected SKU, including bundled OEM variants.

Social activity97

Community discussion across Reddit, Mastodon, and other social sources.