Skip to main content
Mallory
CriticalExploited in the wildCISA KEVPublic exploitVulnerability

CVE-2019-0604: Microsoft SharePoint XML Deserialization Remote Code Execution

Published Mar 6, 2019 · Updated 12 days ago
Trending this weekNot trendingOutside this week’s top 100
Mention activity · 30 daysNo mention activity in the last 30 days.
CVSS9.8Critical · v3.1
EPSS99.9%100th percentile
CISA KEVYesAdded Nov 3, 2021
In the wildActivePer CISA KEV
Vendor
Microsoft Corporation
IdentifiersCVE-2019-0604CWE-502

CVE-2019-0604 is a remote code execution vulnerability in Microsoft SharePoint involving insecure XML deserialization and insufficient validation of application-package source markup. Crafted input can cause arbitrary code execution in the context of the SharePoint application pool and server farm account. Affected products include SharePoint Server 2019, SharePoint Enterprise Server 2016, SharePoint Server and Foundation 2013 SP1, and SharePoint Server and Foundation 2010 SP2. The vulnerability has been actively exploited to install web shells and facilitate subsequent malware deployment.

Do you run this?See affected versions in your environment and whether adversaries are exploiting this vulnerability against assets like yours.
Check your exposure
Analyst brief

Impact, mitigation & remediation

What it means and what to do now: patch path, interim mitigations, and the assume-compromise checklist.

Impact

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

Successful exploitation compromises the affected SharePoint server within the permissions of its application pool and farm account, exposing accessible information and permitting unauthorized modification and command execution. Observed follow-on activity includes persistent web shells, reconnaissance, data exfiltration, Cobalt Strike deployment, and Hello/WickrMe ransomware. Attackers have also used compromised SharePoint servers to reach domain controllers and exploit Zerologon; domain-wide compromise requires additional access or vulnerabilities and is not an intrinsic outcome of CVE-2019-0604 alone.

Mitigation

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

Until all required updates are installed, restrict network access to vulnerable SharePoint services, particularly internet-facing deployments. Correlate IIS request logs with endpoint alerts to identify web-shell installation and activity, suspicious commands launched by IIS worker processes, and unexpected server-side scripts. Investigate suspected compromise and initiate containment and recovery procedures. Access restrictions and monitoring reduce exposure but do not correct the underlying vulnerability.

Remediation

Patch, then assume compromise.

Install all Microsoft security updates applicable to the affected SharePoint installation, or supported superseding updates. Relevant updates include KB4462199 for SharePoint Server 2019; KB4462211 for SharePoint Enterprise Server 2016; KB4462202 and KB4462143 for applicable SharePoint 2013 products; and KB4462184 and KB4461630 for applicable SharePoint 2010 products. Microsoft issued additional updates on March 12, 2019, and clarified on April 25, 2019, that some installations require two update downloads for full protection. Do not assume the initial February 2019 update alone is sufficient. Investigate previously exposed servers for compromise and remove attacker persistence; patching does not remove existing web shells or backdoors.

Public exploits

Exploits

3 exploits validated by Mallory's analysis. Hidden: 1 not yet analyzed, such as Exploit-DB entries.

View more in app →
CVE-2019-0604This repository contains a Python exploit script (cve-2019-0604-exp.py) targeting Microsoft SharePoint servers vulnerable to CVE-2019-0604, a remote code execution flaw. The exploit works by sending crafted requests to the SharePoint Picker.aspx endpoint, leveraging the vulnerability to upload a web shell (ua.aspx) to the server. Once the shell is uploaded, the script attempts to access it to verify successful exploitation. The main file is a standalone Python script, and the only other file is a README with references to further documentation. The exploit requires the attacker to provide the base URL of the target SharePoint instance. The script is operational and provides a working web shell if the target is vulnerable.k8gege · Disclosed Jun 26, 2019 · python · networkOperationalweaponized-0604This repository is a weaponized exploit for CVE-2019-0604, a critical remote code execution vulnerability in Microsoft SharePoint. The main exploit logic is in 'exploit.py', which automates the exploitation process, supporting both direct command execution and file upload (such as webshells) to the target SharePoint server. The exploit can operate in both authenticated and unauthenticated modes, depending on the target's configuration. It supports out-of-band (OOB) exfiltration of command output via DNS or HTTP channels, integrating with services like Burp Collaborator or requestbin.net. The payloads are serialized XAML objects that trigger the vulnerability, and the repository includes helper scripts for request parsing, payload generation, and OOB data handling. The structure is modular, with separate files for SharePoint-specific payload crafting ('sharepointkit.py'), OOB handling ('oob/collab_handler.py', 'oob/decoder.py'), and a sample PowerShell webshell ('oob/payload.ps1'). The exploit is operational and can be used to gain remote code execution, upload arbitrary files, and retrieve output from the target system.Gh0st0ne · Disclosed Apr 22, 2021 · python · powershell · networkOperationalCVE-2019-0604This repository is a proof-of-concept exploit for CVE-2019-0604, a remote code execution vulnerability in Microsoft SharePoint. The main code is in 'ConsoleApplication1/ConsoleApplication1/Program.cs', a C# console application that demonstrates how a malicious XAML file (t.xml) can be used to trigger code execution via SharePoint's deserialization of XAML. The exploit leverages the 'ObjectDataProvider' in XAML to launch arbitrary commands (e.g., 'cmd.exe /c calc'). The repository includes the XAML payload (t.xml) and the C# code that loads and executes it, simulating the vulnerable SharePoint behavior. No network endpoints or hardcoded IPs are present, but the attack vector is network-based, targeting SharePoint servers that process attacker-supplied XAML. The exploit is a POC and does not include weaponized or automated exploitation scripts.linhlhq · Disclosed Mar 23, 2019 · csharp · xaml · networkPoC
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 Enterprise Serverapplication
Microsoft CorporationSharepoint Foundationapplication
Microsoft CorporationSharepoint Serverapplication
FAQ

Frequently asked questions

Is CVE-2019-0604 exploited in the wild?
Yes. As of Nov 5, 2026, Mallory has reports of exploitation in the wild, and CISA added it to KEV on Nov 3, 2021.
Is there a public exploit for CVE-2019-0604?
Yes. Mallory tracks 3 public exploits or proofs of concept for CVE-2019-0604, the earliest disclosed Mar 23, 2019.
Is there a patch for CVE-2019-0604?
Install all Microsoft security updates applicable to the affected SharePoint installation, or supported superseding updates. Relevant updates include KB4462199 for SharePoint Server 2019; KB4462211 for SharePoint Enterprise Server 2016; KB4462202 and KB4462143 for applicable SharePoint 2013 products; and KB4462184 and KB4461630 for applicable SharePoint 2010 products.
What products are affected by CVE-2019-0604?
Microsoft Corporation Sharepoint Enterprise Server, Microsoft Corporation Sharepoint Server, and Microsoft Corporation Sharepoint Foundation.
How severe is CVE-2019-0604?
CVE-2019-0604 has a CVSS v3.1 score of 9.8 (Critical) and an EPSS score of 99.9% (100th percentile) as of Nov 5, 2026.
Mallory platform

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, and which detections to deploy tonight.
Exposure mappingQuery your assets running an affected version, and investigate the blast radius.
Threat actor evidence20Every report linking this CVE to a named adversary.
Associated malware31Malware families linked to this CVE, with evidence and IOCs.
Detection signatures2YARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.
Vendor-by-vendor mappingCross-references every affected SKU, including bundled OEM variants.
Social activityCommunity discussion across Reddit, Mastodon, and other social sources.