CISA Adds Actively Exploited SharePoint RCE Chain to KEV Catalog, Mandates Federal Patching

CISA Warns of Actively Exploited Microsoft SharePoint Vulnerabilities, Adds Two to KEV Catalog

CRITICAL
March 12, 2026
4m read
VulnerabilityCyberattackRegulatory

Related Entities

Organizations

CVE Identifiers

CVE-2023-29357
CRITICAL
CVE-2023-24955
HIGH

Full Report

Executive Summary

The US Cybersecurity and Infrastructure Security Agency (CISA) has issued a directive adding two Microsoft SharePoint Server vulnerabilities to its Known Exploited Vulnerabilities (KEV) catalog. The vulnerabilities, CVE-2023-29357 and CVE-2023-24955, can be chained by an unauthenticated attacker to achieve remote code execution (RCE) with the privileges of the SharePoint server. Due to evidence of active exploitation, CISA has mandated that federal agencies patch these flaws. This warning serves as a critical alert for all public and private sector organizations running on-premise SharePoint servers to verify they are patched and secure.


Threat Overview

The attack combines two powerful vulnerabilities:

  1. CVE-2023-29357 (CVSS 9.8 - Critical): An authentication bypass/privilege escalation vulnerability. It allows a remote, unauthenticated attacker to impersonate any user, including administrators, by sending a specially crafted API request containing a spoofed JSON Web Token (JWT).
  2. CVE-2023-24955 (CVSS 7.2 - High): A command injection/remote code execution vulnerability. An authenticated attacker with Site Owner permissions can inject and execute arbitrary commands on the server.

By chaining these two, an attacker can first use CVE-2023-29357 to gain administrator privileges without needing credentials. Then, using those elevated privileges, they can exploit CVE-2023-24955 to execute code on the underlying server, achieving a full, unauthenticated RCE.

Technical Analysis

The attack chain is dangerously simple and effective:

  1. Privilege Escalation: The attacker sends a malicious request to a SharePoint API endpoint, including a JWT with the "alg":"none" header. Due to the flaw, the server accepts this unsigned token, allowing the attacker to impersonate a site administrator.
  2. Remote Code Execution: Now authenticated as an administrator, the attacker leverages the privileges to exploit the second vulnerability, CVE-2023-24955. This involves manipulating a SharePoint application page to execute arbitrary PowerShell commands in the context of the SharePoint server's service account.

MITRE ATT&CK TTPs:

Impact Assessment

A successful exploit of this vulnerability chain leads to a complete compromise of the SharePoint server. The impact includes:

  • Data Theft: Attackers can access, exfiltrate, or delete all data stored within the SharePoint environment, which often includes sensitive corporate documents, intellectual property, and PII.
  • Network Pivot: The compromised SharePoint server can be used as a beachhead to launch further attacks into the internal corporate network.
  • Ransomware Deployment: Threat actors can use their access to deploy ransomware, not just on the SharePoint server but potentially across the entire network.
  • Persistence: Installation of web shells or other backdoors allows for long-term, stealthy access to the organization's network.

Detection & Response

  • Check Patch Status: The highest priority is to verify that the June 2023 (or later) Security Updates for Microsoft SharePoint Server have been applied. Use vulnerability scanners to confirm.
  • Review IIS Logs: Hunt for suspicious requests in the SharePoint server's IIS logs. Look for API calls that are unusual or requests containing JWTs with "alg":"none". Specifically, look for requests to endpoints like /_api/sp.identity.setauthenticated.
  • Monitor Process Creation: Use an EDR to monitor for suspicious child processes spawned by the SharePoint application pool process (w3wp.exe), such as cmd.exe, powershell.exe, or other reconnaissance commands (whoami, ipconfig).
  • D3FEND Techniques: Implement D3-NTA: Network Traffic Analysis to detect anomalous requests to SharePoint API endpoints. Use D3-WPA: Web Protocol Anomaly Detection to flag malformed JWTs or other protocol-level attacks.

Mitigation

  1. Patch Immediately: Apply the security updates released by Microsoft in June 2023 or later. This is the only way to fix the root cause of the vulnerabilities.
  2. Reduce Attack Surface: If possible, restrict access to your SharePoint server from the internet. If it must be internet-facing, place it behind a Web Application Firewall (WAF) with rules designed to inspect and block malicious SharePoint-related traffic.
  3. Enable Logging: Ensure that detailed logging is enabled for both SharePoint (ULS logs) and IIS, and that these logs are being ingested into a SIEM for correlation and analysis.
  4. Least Privilege for Service Accounts: Ensure the SharePoint service account runs with the minimum necessary privileges to function, which can help limit the impact of a successful RCE.

Timeline of Events

1
March 12, 2026
This article was published

MITRE ATT&CK Mitigations

Applying the June 2023 (or later) security updates for SharePoint Server is the only definitive way to remediate these vulnerabilities.

Mapped D3FEND Techniques:

Use a Web Application Firewall (WAF) to filter and inspect traffic to the SharePoint server, potentially blocking exploit attempts at the network edge.

Mapped D3FEND Techniques:

Audit

M1047enterprise

Continuously monitor IIS logs, Windows Event Logs, and SharePoint ULS logs for signs of compromise, such as anomalous process creation or suspicious API calls.

Mapped D3FEND Techniques:

D3FEND Defensive Countermeasures

The active exploitation of this vulnerability chain makes patching an immediate, critical priority. All organizations running on-premise Microsoft SharePoint Server must verify that the June 2023 Security Update (or a more recent cumulative update) is installed. Use enterprise vulnerability scanning tools to confirm the patch status across all SharePoint farms. For multi-server farms, ensure the patch is consistently applied to every server role (Web Front End, Application, etc.). Given the severity and CISA KEV status, any unpatched, internet-facing SharePoint server should be considered compromised until proven otherwise.

To detect attempts to exploit CVE-2023-29357, security teams should configure their WAF, IDS, or network monitoring tools to inspect the Authorization header of incoming HTTP requests to SharePoint servers. Specifically, create a rule to flag any request containing a JSON Web Token (JWT) that specifies "alg":"none". This is a clear indicator of an attempt to bypass authentication, as legitimate tokens must be signed with a cryptographic algorithm. Alerting on this anomaly can provide an early warning of an attack, even before RCE is achieved. This detection should be treated as a high-confidence indicator of malicious activity and trigger an incident response playbook.

Sources & References

Article Author

Jason Gomes

Jason Gomes

• Cybersecurity Practitioner

Cybersecurity professional with over 10 years of specialized experience in security operations, threat intelligence, incident response, and security automation. Expertise spans SOAR/XSOAR orchestration, threat intelligence platforms, SIEM/UEBA analytics, and building cyber fusion centers. Background includes technical enablement, solution architecture for enterprise and government clients, and implementing security automation workflows across IR, TIP, and SOC use cases.

Threat Intelligence & AnalysisSecurity Orchestration (SOAR/XSOAR)Incident Response & Digital ForensicsSecurity Operations Center (SOC)SIEM & Security AnalyticsCyber Fusion & Threat SharingSecurity Automation & IntegrationManaged Detection & Response (MDR)

Tags

CISAKEVSharePointCVE-2023-29357CVE-2023-24955RCEMicrosoft

📢 Share This Article

Help others stay informed about cybersecurity threats