On this page (6 sections)
A critical vulnerability, CVE-2026-120002, was published on 2026-11-10 for Microsoft Office SharePoint. According to the NVD record, it is an incorrect authorization flaw that allows an authorized attacker to elevate privileges over a network. The record lists a CVSS score of 9.9.
Anyone who runs SharePoint, or manages it for a client, should pay attention. The public record is short, so this article separates what is confirmed from what is still unknown, and focuses on how to prepare while details arrive.
What happened
The NVD entry, published 2026-11-10, describes the flaw in a single sentence: incorrect authorization in Microsoft Office SharePoint allows an authorized attacker to elevate privileges over a network. The only reference attached is the Microsoft Security Response Center entry for the CVE at msrc.microsoft.com.
Only one independent publisher covers this story so far, and that source is the NVD record itself. Nothing here has been confirmed by a second, independent party, so treat the details as preliminary.
What we know and what we do not
| Question | Status |
|---|---|
| Is it critical? | Yes, CVSS 9.9 per the NVD record |
| What kind of flaw? | Incorrect authorization (CWE-863) |
| Does the attacker need an account? | The description says an authorized attacker, so some level of access is required |
| Is it remotely reachable? | The description says privileges are elevated over a network |
| Which SharePoint versions are affected? | Not stated in the research |
| Is a patch available? | Not confirmed in the research; check the Microsoft advisory |
| Is it being exploited? | No exploitation reported in the research; no CISA KEV entry |
Technical background: what incorrect authorization means
CWE-863 describes software that performs an authorization check, but performs it wrongly. The application knows who the user is, yet it fails to correctly decide what that user is allowed to do. In a collaboration platform like SharePoint, that can mean a user with limited rights is able to act with the permissions of a more privileged role.
This is different from an authentication bypass, where an attacker needs no valid login. Here the description says the attacker is authorized, meaning they already hold some valid access. The risk is the jump from a low-privilege account to a higher one. In practice, low-privilege accounts are common: employees, contractors, guest users and compromised credentials from phishing can all fit that starting point.
The research gives no further technical detail, such as the affected component, the request path or the privilege level gained. We are not going to guess at those, and there is nothing here that would help anyone reproduce the issue.
Who is realistically exposed
- Organizations running SharePoint on their own servers, where patching is their responsibility.
- Sites that let many people sign in, including external partners or guests, because more accounts means more possible starting points.
- Intranets or portals exposed to the internet, since the flaw is described as exploitable over a network.
- Agencies and hosting providers that manage SharePoint for clients and need to know which builds are deployed.
The research does not say whether Microsoft-hosted SharePoint services are affected or already handled. Check the Microsoft advisory for that point rather than assuming.
What to do now
- Open the Microsoft advisory for CVE-2026-120002 and note the affected products, builds and any fixed versions or updates listed.
- Inventory every SharePoint server you run or manage and record its current version and patch level.
- If a fix is listed for your version, schedule it urgently, test it on a staging copy first, and apply it to production.
- Review who holds accounts on SharePoint. Remove unused accounts, expired guests and stale contractor access.
- Reduce network exposure: if SharePoint does not need to be reachable from the internet, restrict it to a VPN or trusted network ranges.
- Review site collection admin and farm administrator memberships for unexpected additions.
- Make sure you have recent, tested backups before patching.
- Re-check the advisory and the NVD record over the next days, since details and exploitation status may change.
Detection and monitoring
Because the flaw is about privilege escalation by an already authorized user, the clearest warning signs are changes in who has what rights. Without more technical detail we cannot name specific log signatures, so focus on general signals:
- Unexpected additions to administrator or owner groups, or permission changes you did not make.
- Accounts performing actions far outside their normal role, such as a regular user changing site settings.
- New or modified sites, workflows or apps that nobody on your team created.
- Unusual sign-in patterns for low-privilege accounts shortly before permission changes.
If you have audit logging enabled in SharePoint, make sure it is retained long enough to look back over the period before you patch. If you find signs of misuse, follow a standard incident process; our guide on what to do when a website is hacked covers the first steps.
For the public-facing side of your environment, outside-in checks such as certificate expiry, DNS changes and header changes are still worth watching. Webforta Monitor covers those kinds of changes, though it does not detect or fix this specific flaw. A website firewall can add a layer in front of web applications, but it is not a substitute for installing the vendor fix.
For broader habits that reduce the impact of any account-based flaw, such as least-privilege access and regular reviews, 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.
