External risk intelligence

SharePoint Server Cross-Site Scripting Allows Attacker Spoofing

CVE advisorySeverity: CRITICAL (CVSS 9.0)

CVE-2025-64672

SharePoint Server is commonly deployed as an internet-facing web application or enterprise portal. While this specific cross-site scripting vulnerability requires an authorized user, the product itself is frequently exposed to public network environments as part of its standard role in supporting external collaboration and business services.

Cross-site Scripting

Microsoft Sharepoint Server

before 16.0.19127.20378

Halo Surface Signal: 4 out of 5 — likely to be public-facing.

External exposure likelihood

Horizon Alert

Summary of the vulnerability and why it matters

This vulnerability in Microsoft Office SharePoint involves improper handling of web page inputs, which an authenticated attacker could exploit to perform spoofing attacks over a network. The primary concern is to confirm if SharePoint Server, a commonly internet-facing application, is deployed in your environment and assess potential exposure.

  • Input handling flaw allows attacker spoofing.
  • SharePoint is often internet-facing.
  • Confirm relevance and exposure.

Attack Path

How an attacker could exploit the issue

An authorized attacker can leverage this vulnerability by tricking a SharePoint user into visiting a malicious link, leading to spoofing. The attacker does not need to exploit the vulnerability directly but rather relies on the user's interaction to trigger the malicious code within the web page generation process. This could allow the attacker to impersonate the user, potentially leading to further malicious actions.

  • Requires an authenticated user.
  • Triggered by user interaction with a crafted link.
  • Risk of user impersonation and spoofing.

Live Threat

Current exploitation, exposure, and threat context

This vulnerability could allow an authenticated attacker to conduct spoofing attacks when a user views a specially crafted web page. This may impact service integrity and lead to unauthorized actions when supported by the advisory.

  • System data could be at risk.
  • Attacker could spoof content.
  • Service integrity may be compromised.

Operational Fix

Recommended remediation, mitigation, and detection steps

This critical cross-site scripting vulnerability in Microsoft SharePoint Server requires immediate attention from teams responsible for application and infrastructure security. The first practical step is to locate all instances of SharePoint Server within your environment, determine their exposure, and identify the accountable system owner. Once confirmed, a risk-based remediation plan should be developed, potentially involving vendor coordination and maintenance window scheduling.

  • Application and Infrastructure owners should prioritize this.
  • Verify SharePoint Server exposure and reachability.
  • Plan remediation based on identified risk.

Supplementary metadata

Validate whether this threat affects your internet-facing exposure.

Halo Threat Intelligence helps prioritize remediation with Halo Surface Signal and H/A/L/O context. Start exposure validation with a free external attack surface trial.

Frequently asked questions

What is Microsoft SharePoint Server?

SharePoint Server is a web-based collaboration and document management platform widely used by organizations to host internal portals, share files, and manage business workflows. It acts as a central hub where teams store, organize, and access information, often serving as a primary interface for enterprise content and team communication.

How does CVE-2025-64672 work?

This vulnerability is classified as Cross-Site Scripting (CWE-79). It occurs when the software improperly handles user-provided data during the generation of a web page. Because the application fails to properly neutralize this input, an attacker can inject malicious scripts that execute in the context of another user's session, leading to potential content spoofing.

What triggers this SharePoint vulnerability?

The vulnerability requires an authenticated user to click or navigate to a specially crafted link. It does not trigger automatically through background network traffic; the attacker must successfully trick a user into interacting with the malicious content. If users do not interact with such links, the specific attack vector remains inactive.

Is my environment at risk from this CVE?

Per Halo Surface Signal, you should prioritize this if your SharePoint instances are internet-facing. Because SharePoint is frequently deployed to support external collaboration and business services, instances accessible over the public network are higher risk than those restricted to internal-only segments.

How should I respond to this threat?

Begin by auditing your infrastructure to locate all active SharePoint Server deployments and identify the system owners responsible for each. Verify whether your versions are affected by checking against the vendor's update guide. Once identified, coordinate with your IT and infrastructure teams to schedule necessary maintenance or apply patches to mitigate the vulnerability.

References