LiveActive security incident?Get immediate response
CVE Record

CVE-2025-53770: Microsoft SharePoint Server Remote Code Execution Vulnerability

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.

CriticalCVSS 9.8Known exploitedUpdated
Glexia's TakeSource changedcritical

Security readout for executives and security teams

Plain-English summary

This critical flaw lets an unauthenticated network attacker run code on vulnerable on-premises SharePoint servers. Successful exploitation could expose documents, alter systems, disrupt services, and enable broader compromise. Microsoft reports exploitation in the wild, and CISA lists the vulnerability as known exploited.

Executive priority

Immediate, highest-priority action is warranted. Assign accountable owners for exposure identification, mitigation, updating, and compromise assessment. Because exploitation is confirmed, remediation alone is insufficient for systems that were reachable while vulnerable; leadership should require evidence of both protection and incident review.

Technical view

CVE-2025-53770 is an untrusted-data deserialization vulnerability, CWE-502, affecting listed on-premises SharePoint Server products. It is remotely reachable, requires no privileges or user interaction, and can compromise confidentiality, integrity, and availability. CVSS 3.1 score: 9.8.

Likely exposure

Exposure is highest for network-accessible or internet-facing SharePoint Enterprise Server 2016, SharePoint Server 2019, and SharePoint Server Subscription Edition deployments. The bundle lists version 16.0.0 for each product but does not provide precise vulnerable build ranges, so administrators must confirm applicability through Microsoft’s advisory.

Exploitation context

Active exploitation is confirmed by Microsoft, and CISA includes CVE-2025-53770 in its Known Exploited Vulnerabilities catalog. The bundle also states that an exploit exists publicly or operationally. It does not establish which organizations are targeted, the total attack scale, or specific compromise indicators.

Researcher notes

The source bundle supports unauthenticated network RCE through unsafe deserialization and confirmed exploitation. It does not provide vulnerable build boundaries, exploit-chain details, reliable indicators, or named update identifiers. Avoid inferring those details. Validate current remediation requirements directly against Microsoft because the bundled description reflects an earlier update-preparation state.

Mitigation direction

  • Review Microsoft’s current advisory for applicable security updates and deployment instructions.
  • Apply Microsoft’s documented mitigation immediately wherever updating cannot be completed.
  • Restrict network access to affected SharePoint servers until protections are verified.
  • Treat previously exposed vulnerable servers as potentially compromised and begin incident-response review.
  • Prioritize backups and recovery readiness before performing emergency remediation.

Validation and detection

  • Inventory all on-premises SharePoint servers, editions, versions, and externally reachable interfaces.
  • Compare installed build and update levels with Microsoft’s current CVE advisory.
  • Verify Microsoft’s documented mitigation is enabled and operating as intended.
  • Review SharePoint, web, authentication, and endpoint telemetry for anomalous activity.
  • Escalate suspicious findings for forensic investigation; the bundle provides no specific indicators.
Prepared
Confidence
high
Sources
5

The source record changed after analysis: Material source record changed after analysis.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

cwe · medium confidence lookup

CWE-502: Code execution behavior lookup

Code execution and unsafe deserialization weaknesses often justify reviewing execution behavior and process telemetry. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.

Open ATT&CK lookup
description · low confidence lookup

Execution behavior lookup

The CVE wording references code or command execution, so execution technique review may help defensive triage. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.

Open ATT&CK lookup
cve · low confidence lookup

CVE-2025-53770 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
Critical
CVSS
9.8 (3.1)
Known Exploited
Yes
Published

Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H/E:F/RL:W/RC:C

Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

1CVSS vectors
5Timeline events
2ADP providers
14Source links

CISA KEV status

Status
Known exploited
Source
CISA-ADP
Date added
KEV reference

SSVC decision data

CISA-ADPCISA Coordinator
Timestamp
Version
2.0.3
Exploitation: activeAutomatable: yesTechnical Impact: total

CVSS vector scores

1 official score

We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.

ScoreVersionSeverityVectorExploitImpactSource
9.8CVSS 3.1CriticalCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H/E:F/RL:W/RC:C3.95.9microsoft

Vulnerability scoring details

Base CVSS 3.1 score

9.8Critical
CVSS 3.1 vector shape for CVE-2025-53770Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H/E:F/RL:W/RC:C

Attack Vector
NetworkAdjacentLocalPhysical
Attack Complexity
LowHigh
Privileges Required
NoneLowHigh
User Interaction
NoneRequired
Scope
ChangedUnchanged
Confidentiality Impact
HighLowNone
Integrity Impact
HighLowNone
Availability Impact
HighLowNone

Vulnerability timeline

Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.

  1. CVE reservedCVE Program

    The CVE ID was reserved by the assigning CNA.

  2. Added to KEVCISA-ADP

    CISA Known Exploited Vulnerabilities metadata lists this CVE as known exploited.

  3. ADP timelineCISA-ADP

    CVE-2025-53770 added to CISA KEV

  4. CVE publishedCVE Program

    The CVE record was published.

  5. CVE updatedCVE Program

    The CVE record metadata indicates this as the latest update time.

ADP provider summaries

CISA-ADPCISA ADP Vulnrichment
other:kevother:ssvc
  • 2025-07-20T00:00:00.000Z: CVE-2025-53770 added to CISA KEV
CVECVE Program Container
Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
MicrosoftMicrosoft SharePoint Enterprise Server 201616.0.0Listed
MicrosoftMicrosoft SharePoint Server 201916.0.0Listed
MicrosoftMicrosoft SharePoint Server Subscription Edition16.0.0Listed
Weakness

CWE details

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.

CWE-502 · source CWE mapping

Deserialization of Untrusted Data

Deserialization of Untrusted Data represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.