cve.bz

CVE-2025-53770 (ToolShell) Microsoft SharePoint Deserialization of Untrusted Data Vulnerability

9.8 criticalKEVExploitEPSS >99.9%

Known as ToolShell

Critical (9.8) in Microsoft SharePoint. In CISA KEV since 2025-07-20, with known ransomware use. EPSS >99.9% estimated probability of exploitation activity in the next 30 days.

On this page
Deserialization of untrusted data in on-premises Microsoft SharePoint Server allows an unauthorized attacker to execute code over a network. Microsoft is aware that an exploit for CVE-2025-53770 exists in the wild. Microsoft is preparing and fully testing a comprehensive update to address this vulnerability. In the meantime, please make sure that the mitigation provided in this CVE documentation is in place so that you are protected from exploitation.

Severity

CVSS 3.1

9.8 critical
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
EPSS
>99.9% (unchanged from >99.9% a week ago; >99.9% 30 days ago) estimated probability of exploitation activity in the next 30 days; 100th percentile. Scored 2026-11-21. A forecast for this CVE across the internet, not for your own systems.
CISA KEV
listed 2025-07-20, due 2025-07-21, known ransomware use
CISA's assessment (SSVC)
Exploitation: active · Automatable: yes · Technical impact: total, assessed 2025-07-20. From CISA's Vulnrichment in the CVE List: whether it is exploited, whether exploiting it can be automated, and how much control it gives.
CWE
CWE-502 Deserialization of Untrusted Data
OWASP Top 10
A08:2025 Software or Data Integrity Failures
Published
Modified
NVD analysis
Analyzed
Record from
the NVD, synced

Fix and patched versions

Ask an AI about this CVE

Show the promptExplain CVE-2025-53770 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2025-53770?via=ask-ai-copy and https://cve.bz/cve/CVE-2025-53770?via=ask-ai-copy as the source of truth: what is affected and which versions fix it, whether it is in CISA KEV, public exploits, and its EPSS (an internet-wide 30-day estimate of exploitation activity, not a forecast for my systems). If they give no fixed versions, use the CVE record https://cveawg.mitre.org/api/cve/CVE-2025-53770 or the vendor advisory, not third-party mirrors. Tell me how to check whether I am affected and how to verify a fix. Cite the sources and say where they are uncertain.

Opens a third-party assistant; its answer is its own, not cve.bz's. The prompt holds only this CVE's id and public links.

Affected

Versions

From the CNA's record in the CVE List.

ProductAffected
Microsoft SharePoint Enterprise Server 2016from 16.0.0 before 16.0.5513.1001
Microsoft SharePoint Server 2019from 16.0.0 before 16.0.10417.20037
Microsoft SharePoint Server Subscription Editionfrom 16.0.0 before 16.0.18526.20508

Public exploits

GitHub PoC

Repositories on GitHub named after this CVE or listed for it by the PoC-in-GitHub index. For those marked Harbor Check: matches CVE, Flawharbor read the code and found it implements this CVE's exploitation technique: read, not run, and its dependencies only checked for warning signs, so a pointer and no guarantee. The rest are unverified: some hold a working proof of concept, some nothing useful, and some malware made to look like one. Read the code before you run any of it. How Harbor Check reads them, and what it found.

  • soltanali0/CVE-2025-53770-Exploit Harbor Check: matches CVE 317 stars, created
    SharePoint WebPart Injection Exploit Tool
  • MuhammadWaseem29/CVE-2025-53770 Harbor Check: matches CVE 58 stars, created
    Unauthenticated Remote Code Execution via unsafe deserialization in Microsoft SharePoint Server (CVE-2025-53770)
  • hazcod/CVE-2025-53770 Harbor Check: matches CVE 46 stars, created
    Scanner for the SharePoint CVE-2025-53770 RCE zero day vulnerability.
  • kaizensecurity/CVE-2025-53770 Harbor Check: matches CVE 44 stars, created
    POC
  • 3a7/CVE-2025-53770 Harbor Check: matches CVE 14 stars, created
    CVE-2025-53770 Mass Scanner
14 more

Detection rules

Ways to detect this CVE, not exploit code: the nuclei template that checks a system for it, and the Suricata and Snort rules that name it. A rule set may ship a rule turned off, so check yours by its sid.

Attack patterns (CAPEC)

  • CAPEC-586 Object Injection Likelihood: Medium · Severity: High

The attack patterns MITRE's CAPEC relates to this record's weaknesses, as MITRE names them. Credits.

References

Check your stackJSON