On this page (7 sections)
CVE-2026-80095 is a cross-site scripting (XSS) vulnerability in Microsoft Office SharePoint. According to the NVD record, it allows an authorized attacker to elevate privileges over a network. The record was published on 2026-11-10 and carries a CVSS score of 9, rated critical.
If you run SharePoint, on premises or as part of a hybrid setup, or manage it for clients, treat this as a patching priority once Microsoft's guidance is confirmed for your edition. Public detail is very thin at the moment, so this article separates what is confirmed from what is not.
What is confirmed so far
The only primary source available is the NVD entry, which gives a short description: improper neutralization of input during web page generation in Microsoft Office SharePoint, exploitable by an authorized attacker over a network to elevate privileges. The record points to the Microsoft Security Response Center entry as its reference.
Only one independent publisher covers this story so far, and we have not been able to review the Microsoft advisory text. That means affected builds, fixed builds, patch names, workarounds and any exploitation status are unconfirmed here. Do not rely on this article for version numbers; read the vendor page directly.
What this type of flaw means in practice
Cross-site scripting happens when an application includes user-supplied input in a web page without properly neutralizing it, so the browser treats that input as active script. In SharePoint, content such as pages, lists, comments and form fields is created by many different users and then displayed to others, including administrators.
The description says the attacker must be authorized, so some form of valid account is needed. The stated impact is privilege elevation. A common pattern with this weakness class is that script running in a more privileged user's browser session can act with that user's rights. The description we have does not explain the exact mechanism, so treat that as general background rather than a confirmed detail of this CVE.
Who is realistically exposed
- Organizations running SharePoint where many people can create or edit content, such as intranets, team sites and document portals.
- Environments with guest, partner or contractor accounts, since any authorized account may be enough to meet the precondition.
- Servers reachable from outside the corporate network, because the description says the attack happens over a network.
- Agencies and hosting providers managing SharePoint for several customers.
Which SharePoint editions and builds are affected has not been confirmed in the sources we reviewed. Assume your deployment may be in scope until the vendor advisory says otherwise.
How to check your exposure
Start with an inventory. You need to know which SharePoint servers you run, which build and patch level each one is on, and who holds accounts on them. Use your normal administration tools or patch management records for the build information; we are not giving a specific command here because the sources we reviewed do not cover one.
Then compare each server's build with the affected and fixed builds in the Microsoft advisory for CVE-2026-80095. If the page does not yet list them, check back, since details are often added after first publication.
What to do now
- Open the Microsoft advisory for CVE-2026-80095 and note the affected products, fixed builds and any mitigations.
- Inventory every SharePoint server and record its current build and patch level.
- Schedule the Microsoft security update for the earliest maintenance window once it is confirmed for your edition, starting with internet-facing servers.
- Review who holds accounts on SharePoint, and remove stale, guest and contractor accounts that no longer need access.
- Reduce who can create or edit pages and content, using least privilege for site owners and contributors.
- Review the list of site collection administrators and farm administrators for unexpected entries.
- If you cannot patch yet, limit network exposure of SharePoint, for example by restricting access to a VPN or known address ranges.
- Take a backup or snapshot before patching, and test the update on a staging farm if you have one.
Detection and monitoring after patching
Because this is a privilege escalation issue, the useful question after patching is whether anyone gained rights they should not have. Without exploit details, focus on general signals:
- Unexpected changes to group membership, site permissions or administrator lists.
- New or recently edited pages and list items from accounts that do not normally publish content, especially items containing unusual script content.
- Sign-ins from unfamiliar locations for accounts with edit rights.
- Audit log entries showing permission changes outside of approved change windows.
Browser-side protections are worth reviewing too. A restrictive Content-Security-Policy header can limit the damage of injected script on many web applications, though whether it helps for this specific flaw is not stated in the sources. You can review the headers your public sites send with the free security headers checker, and our guide to security headers explains each one.
What we do not know yet
- The exact affected SharePoint versions and the fixed builds.
- The CVSS vector and who assigned the score of 9.
- Whether the flaw is being exploited. The research data lists no CISA KEV entry and no reports of attacks, but absence of reports is not proof that nobody is exploiting it.
- Whether a workaround exists besides patching.
We treat these as open until Microsoft's advisory or other primary sources confirm them. For general guidance on keeping a business site's software and access under control, see our small business website security guide.
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.
