Skip to main content
CVE Vulnerability Database
Vulnerability Database/CVE-2026-55016

CVE-2026-55016: Microsoft SharePoint Server XSS Vulnerability

CVE-2026-55016 is a cross-site scripting flaw in Microsoft SharePoint Server that enables authorized attackers to perform spoofing attacks. This article covers the technical details, affected versions, and mitigation steps.

Published:

CVE-2026-55016 Overview

CVE-2026-55016 is a stored cross-site scripting (XSS) vulnerability in Microsoft Office SharePoint Server. The flaw stems from improper neutralization of user-supplied input during web page generation [CWE-79]. An authenticated attacker can inject crafted script content that executes in a victim's browser session when the affected page renders. Successful exploitation enables spoofing over the network and can expose limited confidentiality and integrity of user data within the SharePoint context. Microsoft published the advisory on July 14, 2026, and the vulnerability affects SharePoint Server Subscription Edition, SharePoint Server 2019, and SharePoint Server 2016. Exploitation requires low privileges and user interaction, and the scope changes when script executes across the SharePoint trust boundary.

Critical Impact

An authorized attacker can inject persistent script into SharePoint pages to spoof content, hijack sessions in the victim's browser context, and manipulate rendered data across the network.

Affected Products

  • Microsoft SharePoint Server Subscription Edition
  • Microsoft SharePoint Server 2019
  • Microsoft SharePoint Server 2016 (Enterprise)

Discovery Timeline

  • 2026-07-14 - CVE-2026-55016 published to the National Vulnerability Database
  • 2026-07-14 - Microsoft releases security update guidance for CVE-2026-55016
  • 2026-07-15 - Last updated in NVD database

Technical Details for CVE-2026-55016

Vulnerability Analysis

The vulnerability is a cross-site scripting flaw in the SharePoint Server web rendering pipeline. SharePoint fails to properly neutralize attacker-controlled input before including it in dynamically generated pages. When another user loads the affected page, the browser interprets the injected content as executable script within the SharePoint origin. Because SharePoint pages carry authenticated session context, injected script runs with the victim's privileges against SharePoint APIs and DOM. The scope change reflected in the advisory indicates that the impact crosses the security authority that manages the vulnerable component, extending the attack beyond the injecting user's session.

Root Cause

The root cause is missing or insufficient output encoding of user-controllable input when SharePoint constructs HTML responses [CWE-79]. Values sourced from list items, form fields, or page parameters reach the rendered document without contextual escaping suitable for the HTML, attribute, or JavaScript sink where they are placed. This allows script payloads to survive server-side processing and execute client-side.

Attack Vector

Exploitation requires an attacker with valid SharePoint credentials, such as a contributor who can create or edit content. The attacker stores a crafted payload in a SharePoint object that other users will subsequently view. When a victim navigates to the affected page, the injected script executes in their browser. The attacker can then spoof interface elements, exfiltrate limited data visible to the victim, or issue authenticated requests to SharePoint on the victim's behalf. No verified public exploit code or proof-of-concept is available at the time of publication, and the vulnerability is not listed in the CISA Known Exploited Vulnerabilities catalog. The current EPSS probability is 0.335% (25.78 percentile).

Detection Methods for CVE-2026-55016

Indicators of Compromise

  • Unexpected <script> tags, event handler attributes (onerror, onload, onmouseover), or javascript: URIs stored in SharePoint list fields, page content, or metadata columns.
  • Outbound requests from client browsers to attacker-controlled domains originating from SharePoint page contexts.
  • SharePoint audit log entries showing edits to list items or pages by low-privileged accounts followed by anomalous access patterns from other users.

Detection Strategies

  • Inspect ULS logs and IIS logs for POST/PUT requests to SharePoint content endpoints containing HTML control characters, encoded script fragments, or long attribute payloads.
  • Deploy a Content Security Policy (CSP) in report-only mode to surface inline script violations originating from SharePoint pages.
  • Correlate content modification events with subsequent viewer session anomalies such as unusual API calls, permission changes, or token reuse.

Monitoring Recommendations

  • Enable SharePoint auditing for item updates, page edits, and web part modifications across all site collections.
  • Forward SharePoint, IIS, and Windows event logs to a centralized analytics platform for behavioral correlation across users.
  • Alert on anomalous authenticated activity following page views, including bulk downloads, permission grants, and creation of new privileged users.

How to Mitigate CVE-2026-55016

Immediate Actions Required

  • Apply the Microsoft security update referenced in the Microsoft Security Update Guide for CVE-2026-55016 to all SharePoint Server 2016, 2019, and Subscription Edition farms.
  • Audit SharePoint site permissions and remove unnecessary contribute or edit rights that could be used to store XSS payloads.
  • Review recently modified list items, pages, and web parts for embedded script content and remediate any suspicious entries.

Patch Information

Microsoft has released security updates addressing CVE-2026-55016. Refer to the Microsoft Security Update Guide for the specific KB articles and cumulative updates that apply to each supported SharePoint Server version. Administrators should test updates in a staging farm before production deployment and follow Microsoft's documented patching order for SharePoint farms.

Workarounds

  • Enforce a strict Content Security Policy on SharePoint responses to block inline script execution where feasible.
  • Restrict content authoring privileges to trusted users and require review workflows for pages and list items exposed to broad audiences.
  • Configure HTML Field Security settings on affected site collections to limit permitted markup in rich text fields.

Disclaimer: This content was generated using AI. While we strive for accuracy, please verify critical information with official sources.

Default Legacy - Prefooter | Experience the World’s Most Advanced Cybersecurity Platform

Experience the Most Advanced Cybersecurity Platform

See how the world’s most intelligent, autonomous cybersecurity platform can protect your organization today and into the future.