# CVE-2019-0604: Microsoft SharePoint Remote Code Execution

> Attackers can execute arbitrary code remotely by exploiting improper source markup validation in Microsoft SharePoint application packages.

- **Severity:** Critical 9.8 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Yes, since 3 Nov 2021 (CISA KEV), used in ransomware
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 6 Mar 2019
- **Updated:** 21 Oct 2025
- **Also known as:** GHSA-6mr5-xh3f-7vqm

## What is CVE-2019-0604?

CVE-2019-0604 is a critical code injection vulnerability in Microsoft Sharepoint Enterprise Server, published on 6 Mar 2019. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

A remote code execution vulnerability exists in Microsoft SharePoint when the software fails to check the source markup of an application package, aka 'Microsoft SharePoint Remote Code Execution Vulnerability'. This CVE ID is unique from CVE-2019-0594.

Weakness: CWE-20 (Improper Input Validation)

## Which versions are affected by CVE-2019-0604?

It affects 3 products.


Products: Microsoft Sharepoint Enterprise Server, Microsoft Sharepoint Foundation, Microsoft Sharepoint Server.

## How do I fix CVE-2019-0604?

No fix has been published for CVE-2019-0604 yet. Limit exposure of the affected software until one is available. US federal agencies must fix it by 3 May 2022.

## Is CVE-2019-0604 being exploited?

Yes. Attackers have exploited CVE-2019-0604 in the wild since at least 3 Nov 2021, including in ransomware campaigns.

Public exploit code:

- CVE-2019-0604 (github_poc): https://github.com/linhlhq/CVE-2019-0604
- cve-2019-0604 SharePoint RCE exploit (github_poc): https://github.com/k8gege/CVE-2019-0604
- 详解 k8gege的SharePoint RCE exploit cve-2019-0604-exp.py的代码，动手制作自己的payload (github_poc): https://github.com/boxhg/CVE-2019-0604
- Automated tool to exploit sharepoint CVE-2019-0604 (github_poc): https://github.com/Gh0st0ne/weaponized-0604
- CVE-2019-0604: SharePoint RCE detection rules and sample PCAP (github_poc): https://github.com/m5050/CVE-2019-0604
- https://github.com/likekabin/CVE-2019-0604_sharepoint_CVE (github_poc): https://github.com/likekabin/CVE-2019-0604_sharepoint_CVE

## Other vulnerabilities in Microsoft Sharepoint Enterprise Server

- [CVE-2023-24955](https://insights.sbomify.com/CVE-2023-24955/): Microsoft SharePoint Server Code Injection (high 7.2, exploited in the wild)
- [CVE-2025-49706](https://insights.sbomify.com/CVE-2025-49706/): Microsoft SharePoint Improper Authentication (medium 6.5, exploited in the wild)
- [CVE-2020-1210](https://insights.sbomify.com/CVE-2020-1210/): Microsoft SharePoint Remote Code Execution Vulnerability (critical 9.9)
- [CVE-2020-1595](https://insights.sbomify.com/CVE-2020-1595/): Microsoft SharePoint Remote Code Execution Vulnerability (critical 9.9)
- [CVE-2025-47163](https://insights.sbomify.com/CVE-2025-47163/): Microsoft SharePoint Server Remote Code Execution Vulnerability (high 8.8)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2019-0604 and fix it if it is affected.

What it is: CVE-2019-0604 is a critical code injection vulnerability in Microsoft Sharepoint Enterprise Server, published on 6 Mar 2019. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: Yes. Attackers have exploited CVE-2019-0604 in the wild since at least 3 Nov 2021, including in ransomware campaigns.

Affected product: Microsoft Sharepoint Enterprise Server. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2019-0604/ (Markdown: https://insights.sbomify.com/CVE-2019-0604/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2019-0604
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2019-0604
- OSV: https://osv.dev/vulnerability/CVE-2019-0604

---
From sbomify Insights: https://insights.sbomify.com/CVE-2019-0604/
Summaries are generated and may contain mistakes; the official description above is the record.