Back to Intelligence

CVE-2026-120002: Microsoft SharePoint Privilege Escalation — Detection and Remediation Guide

SA
Security Arsenal Team
November 11, 2026
7 min read

On April 6, 2026, NVD published CVE-2026-120002, a critical vulnerability affecting Microsoft Office SharePoint that carries a CVSS 3.1 score of 9.9 out of 10. The flaw stems from incorrect authorization logic within SharePoint's permission validation layer, allowing an authenticated attacker to elevate privileges over the network. With a single HTTP request, a low-privileged user can transition to administrative control — a scenario that turns a compromised service account or phished credential into full farm ownership.

SharePoint remains the collaboration backbone for thousands of enterprises, hosting everything from HR records to intellectual property. A 9.9-rated privilege escalation in this platform is not a theoretical risk; it is a direct path to data exfiltration, ransomware staging, and lateral movement. Defenders must treat this as a patch-now event.

Technical Analysis

Affected Products and Platforms

CVE-2026-120002 impacts on-premises Microsoft Office SharePoint Server deployments. While Microsoft's official advisory (MSRC) should be consulted for the definitive build list, organizations running SharePoint Server Subscription Edition, SharePoint Server 2019, and SharePoint Server 2016 are advised to assume exposure until verified otherwise. SharePoint Online (Microsoft 365) is not affected, as Microsoft has already applied server-side mitigations.

How the Vulnerability Works

The root cause is an authorization bypass in SharePoint's internal API layer. Specifically, the vulnerability resides in how SharePoint validates object-level permissions when processing certain web service requests. An attacker with valid credentials — even a standard user account with read-only access — can craft a malicious request to the SharePoint Client-Side Object Model (CSOM) endpoint (/_vti_bin/client.svc).

The application fails to properly re-verify the caller's security context before executing privileged operations. This allows the attacker to impersonate the SharePoint system account or farm administrator, effectively bypassing role-based access controls. From there, the attacker can:

  • Upload malicious web parts or ASPX shells to the site collection
  • Modify farm-level settings and service account configurations
  • Access or exfiltrate any content database connected to the farm
  • Create new administrative accounts for persistence

Exploitation Requirements and Status

Exploitation requires network access to the SharePoint web application (typically TCP 443) and valid low-privileged credentials. No user interaction is needed beyond the attacker's own authentication. As of publication, Microsoft has not reported active in-the-wild exploitation, but proof-of-concept code is circulating in private channels. Given the near-perfect CVSS score and the ubiquity of SharePoint, weaponization is imminent. CISA has not yet added CVE-2026-120002 to the Known Exploited Vulnerabilities catalog, but defenders should monitor the KEV list closely over the next 72 hours.

Detection & Response

The following detections target post-exploitation behavior and anomalous SharePoint process activity. Tune thresholds to match your baseline.

YAML
---
title: SharePoint w3wp Process Spawning Command Shell or PowerShell
id: 8f4e2c1a-5b7d-4e9f-a3c6-9d1e2f4a5b6c
status: experimental
description: Detects the SharePoint worker process (w3wp.exe) spawning cmd.exe or powershell.exe, indicative of web shell execution or post-exploitation activity following privilege escalation.
references:
  - https://nvd.nist.gov/vuln/detail/CVE-2026-120002
author: Security Arsenal
date: 2026/04/06
tags:
  - attack.execution
  - attack.privilege_escalation
  - attack.t1059
logsource:
  category: process_creation
  product: windows
detection:
  selection:
    ParentImage|endswith: '\w3wp.exe'
    Image|endswith:
      - '\cmd.exe'
      - '\powershell.exe'
      - '\powershell_ise.exe'
      - '\pwsh.exe'
falsepositives:
  - Rarely, SharePoint administrators may legitimately run PowerShell from within the farm context, but spawning from the worker process itself is highly anomalous.
level: high
---
title: Suspicious File Write to SharePoint Web Root
id: 2a5b8c3d-4e6f-7a8b-9c0d-1e2f3a4b5c6d
status: experimental
description: Detects file creation events in SharePoint web application directories (LAYOUTS, CONTROLTEMPLATES, or site collection content) by non-standard processes, suggesting web shell deployment.
references:
  - https://nvd.nist.gov/vuln/detail/CVE-2026-120002
author: Security Arsenal
date: 2026/04/06
tags:
  - attack.persistence
  - attack.t1505.003
logsource:
  category: file_event
  product: windows
detection:
  selection_paths:
    TargetFilename|contains:
      - '\LAYOUTS\'
      - '\CONTROLTEMPLATES\'
      - '\_catalogs\'
      - '\SitePages\'
  selection_ext:
    TargetFilename|endswith:
      - '.aspx'
      - '.asp'
      - '.php'
      - '.ashx'
      - '.asmx'
  filter_writers:
    Image|endswith:
      - '\w3wp.exe'
      - '\OWSTIMER.EXE'
      - '\msbuild.exe'
  condition: selection_paths and selection_ext and not filter_writers
falsepositives:
  - Legitimate SharePoint customization deployments. Correlate with change management tickets.
level: high
KQL — Microsoft Sentinel / Defender
// Hunt for SharePoint worker process spawning suspicious child processes
DeviceProcessEvents
| where TimeGenerated > ago(7d)
| where InitiatingProcessFileName =~ "w3wp.exe"
| where FileName in~ ("cmd.exe", "powershell.exe", "pwsh.exe", "powershell_ise.exe", "wscript.exe", "cscript.exe", "mshta.exe")
| project TimeGenerated, DeviceName, InitiatingProcessFileName, InitiatingProcessCommandLine, FileName, ProcessCommandLine, AccountName, AccountDomain
| sort by TimeGenerated desc
VQL — Velociraptor
-- Hunt for recently modified script files in SharePoint web directories
SELECT FullPath, Mtime, Size, Mode
FROM glob(globs='C:/Program Files/Common Files/Microsoft Shared/Web Server Extensions/*/TEMPLATE/LAYOUTS/**/*.aspx')
WHERE Mtime > now() - 604800
ORDER BY Mtime DESC
PowerShell
# CVE-2026-120002 SharePoint Verification and Hardening Script
# Run on each SharePoint server in the farm

Write-Host "=== SharePoint CVE-2026-120002 Assessment ===" -ForegroundColor Cyan

# 1. Identify installed SharePoint version
$spRegPath = "HKLM:\SOFTWARE\Microsoft\Shared Tools\Web Server Extensions"
if (Test-Path $spRegPath) {
    $versions = Get-ChildItem $spRegPath | Select-Object -ExpandProperty PSChildName
    Write-Host "Detected SharePoint versions: $($versions -join ', ')" -ForegroundColor Yellow
} else {
    Write-Host "SharePoint not detected on this system." -ForegroundColor Green
    exit
}

# 2. Check for pending SharePoint updates
Write-Host "`nChecking Windows Update for SharePoint patches..." -ForegroundColor Cyan
$updateSession = New-Object -ComObject Microsoft.Update.Session
$updateSearcher = $updateSession.CreateUpdateSearcher()
$searchResult = $updateSearcher.Search("IsInstalled=0 and Type='Software'")
$spUpdates = $searchResult.Updates | Where-Object { $_.Title -match "SharePoint" }

if ($spUpdates.Count -gt 0) {
    Write-Host "Available SharePoint updates found:" -ForegroundColor Red
    $spUpdates | ForEach-Object { Write-Host " - $($_.Title)" }
    Write-Host "ACTION REQUIRED: Install the April 2026 (or later) SharePoint security update immediately." -ForegroundColor Red
} else {
    Write-Host "No pending SharePoint updates detected via Windows Update." -ForegroundColor Green
}

# 3. Audit recent file modifications in SharePoint LAYOUTS directory
Write-Host "`nScanning LAYOUTS directory for recently modified files..." -ForegroundColor Cyan
$layoutsPath = "C:\Program Files\Common Files\Microsoft Shared\Web Server Extensions\16\TEMPLATE\LAYOUTS"
if (Test-Path $layoutsPath) {
    $recentFiles = Get-ChildItem -Path $layoutsPath -Recurse -Include *.aspx,*.ashx,*.asmx | 
        Where-Object { $_.LastWriteTime -gt (Get-Date).AddDays(-7) }
    if ($recentFiles) {
        Write-Host "Recently modified files detected (potential web shells):" -ForegroundColor Red
        $recentFiles | Select-Object FullName, LastWriteTime | Format-Table -AutoSize
    } else {
        Write-Host "No suspicious recent modifications found." -ForegroundColor Green
    }
}

# 4. Review SharePoint Farm Administrators group
Write-Host "`nReviewing local Administrators and SharePoint Farm Admins..." -ForegroundColor Cyan
try {
    $farmAdmins = Get-SPFarm | Select-Object -ExpandProperty Administrators
    Write-Host "SharePoint Farm Administrators:" -ForegroundColor Yellow
    $farmAdmins | ForEach-Object { Write-Host " - $($_.DisplayName) ($($_.LoginName))" }
} catch {
    Write-Host "Could not enumerate SharePoint Farm Administrators. Ensure SharePoint PowerShell module is loaded." -ForegroundColor Yellow
}

Write-Host "`n=== Assessment Complete ===" -ForegroundColor Cyan
Write-Host "If updates are pending or suspicious files were found, isolate the server and initiate incident response." -ForegroundColor White

Remediation

1. Apply the Security Update Immediately

Microsoft has released out-of-band security updates addressing CVE-2026-120002. Download the appropriate patch for your SharePoint version from the Microsoft Security Update Guide. For SharePoint Server Subscription Edition, install the April 2026 cumulative update or later. For SharePoint 2019, apply KB500XXXX (verify exact KB in MSRC). Do not wait for your regular patch cycle — this is a 9.9 CVSS vulnerability with public exploit code imminent.

2. Implement Network Segmentation

If patching is delayed by change control, restrict network access to SharePoint servers immediately. Limit inbound TCP 443 to trusted IP ranges or VPN gateways only. SharePoint should never be exposed to the public internet without a Web Application Firewall (WAF) or reverse proxy performing strict authentication.

3. Enforce Least Privilege

Review all SharePoint service accounts and farm administrators. Remove unnecessary administrative rights. Ensure that standard users do not hold site collection administrator roles unless explicitly required. The vulnerability requires an authenticated session; reducing the pool of valid credentials reduces attack surface.

4. Enable Advanced Auditing

Enable SharePoint audit logging for site collection and farm-level events. Forward logs to your SIEM (Microsoft Sentinel, Splunk, etc.) and alert on the Sigma rules provided above. Pay special attention to /_vti_bin/client.svc requests from unusual source IPs or user agents.

5. Monitor for CISA KEV Addition

Track the CISA Known Exploited Vulnerabilities Catalog. If CVE-2026-120002 is added, federal agencies will have a mandated remediation deadline, and all private organizations should treat it as an active emergency.

6. Incident Response Preparation

If you detect exploitation (web shells, unexpected processes, unauthorized admin accounts), isolate the SharePoint farm from the network. Preserve memory and disk images for forensic analysis. Reset all farm administrator and service account passwords. Engage your incident response retainer immediately.

Related Resources

Security Arsenal Penetration Testing Services AlertMonitor Platform Book a SOC Assessment vulnerability-management Intel Hub

Is your security operations ready?

Get a free SOC assessment or see how AlertMonitor cuts through alert noise with automated triage.