On this page (7 sections)

CVE-2026-109454 is a cross-site scripting (XSS) vulnerability in Microsoft Office SharePoint. According to the NVD record, it lets an authorized attacker perform spoofing over a network. The record was published on 2026-11-10 and carries a critical severity rating with a CVSS score of 9.0.

Anyone who runs SharePoint, whether as an internal intranet or a document portal shared with partners, should treat this as a prompt to check Microsoft's guidance. The public record is short, and several details that matter for patching are not available in the research we have, so this article is explicit about what is confirmed and what is not.

What the record says

The entire public description is one sentence: 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. The NVD entry lists Microsoft's update guide as its only reference.

Two details are worth reading carefully. First, the attacker must be authorized, meaning they already hold a valid account or some level of access to the SharePoint environment. Second, the impact is described as spoofing, not remote code execution or data theft. That fits the general pattern of XSS, where content shown to other users is made to look trustworthy when it is not.

Understanding the weakness class

Cross-site scripting happens when an application includes user-supplied input in a web page without properly neutralizing it. The browser then treats attacker-controlled content as part of the legitimate page. In a collaboration platform like SharePoint, where many users create pages, lists, comments and documents that other people view, that creates a path from a low-privileged account to the browsers of other users.

What an attacker can do with that depends on the specific flaw and the victim's permissions. In general terms, XSS can be used to show misleading content, perform actions in the victim's session, or target higher-privileged users such as site owners. The research does not describe how this particular bug works, and we will not speculate beyond the vendor's own wording of spoofing.

Who is realistically exposed

  • Organizations running Microsoft Office SharePoint where many people can create or edit content.
  • Environments that give contractors, partners or guests contributor-level access, since the attacker must be authorized but not necessarily privileged.
  • Teams where administrators regularly browse user-created pages, because those are the most valuable targets of an XSS-style attack.
The research does not list affected SharePoint versions, editions or deployment types (for example on-premises versus online). Do not assume you are safe or affected until you have read Microsoft's advisory for your exact build.

What we do not know yet

Only one independent publisher covers this story so far, and the underlying source is the NVD record, which repeats the vendor description. That leaves several open questions:

  • Which SharePoint versions and builds are affected, and which updates fix the issue.
  • The CVSS vector, which would show how much user interaction is needed and what the impact scope is.
  • Whether the flaw is being exploited. The research shows no CISA KEV listing, but absence from that catalog is not proof that nobody is using it.
  • Whether any workaround or mitigation exists short of patching.

Check the Microsoft Security Response Center entry for these details, and expect them to be filled in over time.

What to do now

  1. Open the Microsoft advisory for CVE-2026-109454 and confirm whether your SharePoint version and edition are listed as affected.
  2. Install the update Microsoft lists for your build, testing first on a staging farm if you have one.
  3. Review who holds contributor, editor or site-owner permissions and remove accounts that no longer need them, including stale guest and contractor accounts.
  4. Ask administrators to avoid opening unfamiliar or recently edited user pages with a privileged account until the patch is applied.
  5. Review recent changes to pages, lists and web parts created by lower-privileged users for content you do not recognize.
  6. Add the CVE to your vulnerability tracker and re-check the advisory in a few days for updated exploitation or mitigation information.
Caution. Applying SharePoint updates can involve service restarts and configuration database upgrades. Schedule a maintenance window and take a backup of the farm before patching.

Hardening and monitoring afterwards

XSS flaws are a recurring class, so it pays to limit the damage of the next one. A strict Content-Security-Policy header can restrict which scripts a browser will run, although it needs careful testing with SharePoint's own scripts. You can check which security headers your SharePoint front end currently sends with the free security headers checker, and the security headers guide explains what each one does.

Keep the principle of least privilege for content authors, review audit logs for unusual page or web part edits, and consider putting internet-facing SharePoint behind a firewall that can filter suspicious requests. For background, see what a WAF is. A WAF is a layer of defense, not a substitute for the vendor update.

Timeline

Known dates from the research
DateEvent
2026-11-10CVE-2026-109454 published in the NVD with a CVSS score of 9.0 and critical severity
2026-11-10Microsoft advisory listed as the reference; no CISA KEV listing recorded

Sources

This article is based on the public sources below. Details can change as vendors and researchers publish more; check the original advisories before acting on version numbers.

  1. CVE-2026-109454: Improper neutralization of input during web page generation ('cross-site scripting') in Microsoft Office SharePoint allows an authorized attacker to perform…nvd.nist.gov ·
  • SharePoint
  • Microsoft
  • XSS
  • CVE-2026-109454
  • spoofing