CVE Tools

CVE-2026-64900

Microsoft SharePoint Server Spoofing Vulnerability

No known exploitation. EPSS puts it in the 49th percentile. A vendor fix is available.

Published Updated Sources: CVE.org, NVD

What to do

The vendor has published a fix. Version details are below where the sources state them.

Steps

Written by AI from the record
  1. Check whether you run one of these Microsoft SharePoint versions: SharePoint Enterprise Server 2016, SharePoint Server 2019, or SharePoint Server Subscription Edition (or confirm your “sharepoint server” build number).
  2. Compare your current SharePoint build to the fixed builds: Enterprise Server 2016 → 16.0.5565.1001; SharePoint Server 2019 → 16.0.10417.20198; Subscription Edition → 16.0.19725.20522.
  3. Upgrade/apply the Microsoft patch for CVE-2026-64900 from the Microsoft Update Guide page linked below.
  4. If you can’t patch immediately, restrict who can create/edit SharePoint pages and reduce exposure by limiting where external or low-privilege users can input content that produces web pages.

What it is

From the CVE record

Improper neutralization of input during web page generation ('cross-site scripting') in Microsoft Office SharePoint allows an authorized attacker to perform spoofing over a network.

In plain language

Written by AI from the record

CVE-2026-64900 is a SharePoint flaw where a logged-in user can plant malicious code in SharePoint pages so that other visitors’ browsers execute it, and typical small businesses should patch if they have affected SharePoint versions with users who can create or edit content.

In Microsoft SharePoint Enterprise Server 2016/2019/Subscription Edition (sharepoint server), an authenticated user with low privileges can inject malicious script into generated web pages (insufficient sanitization of user-generated content), enabling cross-site scripting–style session impact when victims browse the crafted page.

If you're affected

  • User session impersonation
  • Sensitive data theft
  • Brand and login spoofing
  • Compromised user accounts

Exploitation

Where each signal puts this CVE on the scale from published to confirmed exploited.

EPSS49th
CISA KEV

Not in the catalog. CISA has not confirmed exploitation.

Public exploits

No public exploit or proof of concept found in the sources we track.

EPSS

0.6% chance of exploitation activity in the next 30 days, which ranks it in the 49th percentile of scored CVEs.

Exploit Prediction Scoring System, FIRST.org. A probability, not a confirmation.

Lifecycle

11 events over 8 days, from the signal feeds we watch.

  1. Patch availablerecord updated
  2. OpenVAS check added
  3. Patch availablerecord updated
  4. Patch availablepublished, weakness classified, att&ck mapped, record updated, record updated

Affected products

Technical detail

CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:U/C:H/I:H/A:N

Scored 7.3 by NVD.

How it is reached

  • Attack Vector NetworkExploitable remotely over the network without any special conditions
  • Attack Complexity LowNo special conditions — the attack can be reliably reproduced
  • Privileges Required LowRequires basic user-level privileges
  • User Interaction RequiredA user must click a link, open a file, or perform some action

Scope

  • Scope UnchangedImpact is limited to the vulnerable component itself

Impact if exploited

  • Confidentiality HighTotal information disclosure — all data in the component is compromised
  • Integrity HighTotal loss of integrity — attacker can modify any data in the component
  • Availability NoneNo availability impact

Weaknesses

ATT&CK techniques

Mapped from the weaknesses above (CWE to ATT&CK), not observed in attacks.

Sources

Watch the software you run.

My Stack ranks new CVEs for your products by real-world exploitation, so the next serious one reaches you without reading every advisory.

We'll flag the next CVE, public exploit or patch for Microsoft, not every advisory.

We use analytics cookies to see which pages and articles actually help people. Decline and none of them run — the site works the same. What we store