CVE Tools

CVE-2026-70332

Microsoft Office SharePoint Spoofing Vulnerability

No known exploitation. EPSS puts it in the 57th 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. Confirm your business uses Microsoft SharePoint Online (and not only on-prem SharePoint), and identify any users who can access it externally or receive share links.
  2. Check Microsoft’s update page for CVE-2026-70332 and note the recommended service/apply guidance for SharePoint Online; verify your tenant is current according to Microsoft’s instructions.
  3. Reduce exposure immediately: review external sharing settings, restrict who can create or share links, and disable or tightly control any untrusted third-party add-ins/custom scripts that could worsen spoofing risk.
  4. Train users who access SharePoint to treat unexpected SharePoint-looking prompts as suspicious and report them to IT; increase monitoring for unusual sign-ins or unexpected actions in SharePoint.
  5. Document completion and open a ticket with your Microsoft support channel (or IT vendor) referencing CVE-2026-70332 if Microsoft guidance indicates an action you must take at the tenant level.

What it is

From the CVE record

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

In plain language

Written by AI from the record

CVE-2026-70332 is a Microsoft SharePoint Online flaw that can let a remote attacker trick users with a fake page; because it’s tied to very serious security impact, you should review SharePoint Online protections and make sure you’re receiving Microsoft’s latest security fixes.

CVE-2026-70332 is a cross-site scripting (CWE-79) issue in Microsoft Office SharePoint that enables attacker-controlled web content to be rendered in a way that supports network-based spoofing; impact is severe because it can lead to user trust theft and session/user action compromise despite requiring user interaction.

If you're affected

  • User account/session compromise
  • Phishing and credential theft
  • Service disruption
  • Compromised business workflows

Exploitation

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

EPSS57th
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.9% chance of exploitation activity in the next 30 days, which ranks it in the 57th percentile of scored CVEs.

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

Lifecycle

7 events over 1 day, from the signal feeds we watch.

  1. Patch availablerecord updated, record updated, record updated
  2. Publishedweakness classified, att&ck mapped

Affected products

Technical detail

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

Scored 9.6 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 NoneNo authentication required — anyone can exploit this
  • User Interaction RequiredA user must click a link, open a file, or perform some action

Scope

  • Scope ChangedThe exploit can affect other components (e.g. sandbox escape, host compromise from VM)

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 HighTotal denial of service — the component is completely unavailable

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 Sharepoint Online, 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