Skip to content
skopnix

CVE-2023-24955 · Published 9 May 2023

Microsoft SharePoint Server

On CISA's KEV list 322 days after disclosure; 3 public exploits.

Microsoft SharePoint Server contains a code injection vulnerability that allows an authenticated attacker with Site Owner privileges to execute code remotely.

CISA required action (federal due date 16 Apr 2024): Apply mitigations per vendor instructions or discontinue use of the product if mitigations are unavailable.

Signals

KEV, exploited in the wild
yes, added 26 Mar 2024, due 16 Apr 2024, known ransomware use
EPSS, 30-day forecast
85%, 100th percentile (as of 18 Nov 2026)
CVSS, NVD
not stated
Internet exposure
not stated

KEV is an observation, EPSS a forecast; KEV outranks it. No score published by NVD.

Timeline 9 May 2023 to today

233 days from disclosure to the first proof of concept
20252026Disclosed 9 May 2023First PoC 28 Dec 2023Metasploit 19 Jan 2024KEV 26 Mar 2024today
  1. Disclosed
  2. First PoC+233 d
  3. Metasploit+22 d
  4. KEV+67 d

233 days from disclosure to the first proof of concept

Indicators none tied yet

No threat feed has tied an indicator to this CVE yet. Checked every six hours.

On the wire 0 dispatches

No dispatch on our wire has named this CVE yet.

Public exploit code 3 known · links only

GitHub PoCs 2Metasploit 1Exploit-DB 0

GitHub PoCs, by trust then stars2

  1. Exploit for Microsoft SharePoint 2019

    created 28 Dec 2023

  2. first seen by skopnix 18 Oct 2026

Fake proof-of-concept repositories have been used to deliver malware to the researchers who run them. The trust verdict is our engine's heuristic over the repository (account age, what it ships, how its stars arrived); it is a reason to read the code first, not a finding about its author.

Metasploit1

  1. This module exploits two vulnerabilities in Sharepoint 2019, an auth bypass CVE-2023-29357 which was patched in June of 2023 and CVE-2023-24955, an RCE which was patched in May of 2023. The auth bypass allows attackers to impersonate the Sharepoint Admin user. This vulnerability stems from the signature validation check used to verify JSON Web Tokens (JWTs) used for OAuth authentication. If the signing algorithm of the user-provided JWT is set to none, Sh

    ruby · first seen by skopnix 18 Oct 2026

References

Watch this one?

KEV additions reach Telegram and the KEV-only RSS as they land.

Telegram ↗KEV RSSAPIStack check