Microsoft SharePoint Deserialization of Untrusted Data Vulnerability
Exploited since 2025-07-20. 2 of 8 rule sources name it; Cloudflare blocks by default. Our CRS test: blocked.
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… More
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.
Edge coverage
Claimed by vendorsAsk Vigil
AI · answers from this pageWorkers AI (Llama 3.3). Can be wrong: check the cited source.
Severity, decoded
CVSS 3.1Exploitable over the network, with no privileges and no user interaction, leading to full loss of confidentiality, integrity and availability.
How the score is built
- Attack vectorAn attacker can reach it over the internet; no access to your network needed.Network
- Attack complexityNo special conditions are needed; the attack works reliably.Low
- Privileges requiredNo account or login is needed.None
- User interactionNo one has to click or open anything; the attack works on its own.None
- ScopeThe damage stays within the vulnerable component.Unchanged
- Confidentiality impactAn attacker can read all data the affected component holds, or the most sensitive parts of it.High
- Integrity impactAn attacker can change any data or files the affected component protects.High
- Availability impactAn attacker can take the component down completely or keep it from serving anyone.High
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H/E:F/RL:W/RC:CAlso in the vector: Exploit code maturity: Functional · Remediation level: Workaround · Report confidence: Confirmed
Attackers are exploiting this in the wild.
Attackers can script the attack end to end and hit many targets at once.
A successful attack gives full control over the affected software or all of its data.
Public exploits
3 found- MetasploitMicrosoft SharePoint Server ToolPane Unauthenticated Remote Code Execution (aka ToolShell)2025-07-08 · exploit · rank Excellent · has check
- Exploit-DBMicrosoft SharePoint Server 2019 (16.0.10383.20020) - Remote Code Execution (RCE)2025-08-11 · remote · windows
- NucleiCVE-2025-53770.yamldetection template, replayed in our lab
Links are to third-party code: never run it outside an isolated lab.
Timeline
- 2025-07-08Metasploit module publishedMicrosoft SharePoint Server ToolPane Unauthenticated Remote Code Execution (aka ToolShell)
- 2025-07-20CVE publishedCVE List
- 2025-07-20Added to CISA KEVConfirmed exploitation in the wild
- 2025-07-21Cloudflare ships a ruleMicrosoft SharePoint - Deserialization - CVE:CVE-2025-53770
- 2025-08-11Exploit published on Exploit-DBMicrosoft SharePoint Server 2019 (16.0.10383.20020) - Remote Code Execution (RCE)
- 2025-08-15F5 ships a ruleMicrosoft SharePoint ToolPane Remote Code Execution
- 2026-11-02Our test: OWASP Core Rule Set blocked itparanoia level 1, anomaly threshold 5, default CRS settings
- 2026-11-02Our test: OWASP Core Rule Set blocked itparanoia level 2, anomaly threshold 5, default CRS settings
Vendor statements
QuotedCloudflareWAF Managed Rules
First rule 2025-07-21, 1 day after the CVE was published.
Microsoft SharePoint - Deserialization - CVE:CVE-2025-53770. Previous action: N/A. New action: Block. This is a New Detection
AWSAWS WAF Managed Rules
We found no public statement from this vendor naming this CVE. That is not proof of no protection: generic rules may still catch it. AWS often describes a vulnerability without naming its CVE (for example "Log4j"). We count only entries that name the CVE, so AWS coverage is understated.
Microsoft AzureFront Door and Application Gateway WAF (DRS)
We found no public statement from this vendor naming this CVE. That is not proof of no protection: generic rules may still catch it. The rule tables name CVEs but carry no dates, so Azure is left out of every time-to-rule figure.
Google CloudCloud Armor preconfigured WAF rules
We found no public statement from this vendor naming this CVE. That is not proof of no protection: generic rules may still catch it. Google names few CVEs: the release notes start in May 2024 and the rules reference lists CVEs without dates. Its cve-canary rules are opt-in.
FastlyNext-Gen WAF virtual patches
The CVE predates the oldest entry in this vendor's public feed, so a rule may exist that we cannot see.
F5Attack signatures (Distributed Cloud WAF)
First rule 2025-08-15, 26 days after the CVE was published.
Added: signature 200204026 "Microsoft SharePoint ToolPane Remote Code Execution" (Server Side Code Injection, risk High), systems: SharePoint. References: CVE-2025-49704, CVE-2025-49706, CVE-2025-53770, CVE-2025-53771.
AkamaiApp & API Protector (Adaptive Security Engine)
This vendor publishes no machine-readable rule changelog we can check.
OWASP CRSCore Rule Set (open source, used inside many WAFs)
We found no public statement from this vendor naming this CVE. That is not proof of no protection: generic rules may still catch it. CRS rarely names CVEs: it relies on generic detections. Our own lab measures what it actually blocks.
Social
No posts seen yet on X, Bluesky, Mastodon, Hacker News or GitHub.