Loading vulnerability…
CVE-2020-16952 is a remote code execution vulnerability in Microsoft SharePoint caused by inadequate validation of source markup in SharePoint application packages. A specially crafted application package can bypass the expected source-markup checks and enable execution of arbitrary code.
Mallory correlates every CVE against your assets, your vendors, and active adversary campaigns. Know which vulnerabilities matter for you, not just which ones are loud.
What it means. What to do now. Patch path, mitigations, and the assume-compromise checklist.
What an attacker gets, and what they’ve been doing with it.
If you can’t patch tonight, do this now.
Patch, then assume compromise.
1 valid exploit after Mallory filtered fakes, detection scripts, and README-only repos.
This repository contains a single Metasploit module (modules/exploits/windows/http/sharepoint_ssi_viewstate.rb) that exploits CVE-2020-16952, a vulnerability in Microsoft SharePoint (2013, 2016, 2019) on Windows. The exploit leverages a server-side include (SSI) vulnerability to leak the web.config file, from which it extracts the ViewState validation key. With this key, the module forges a malicious ViewState payload to achieve remote code execution (RCE) as an authenticated user with page creation privileges. The exploit supports multiple payloads, including PowerShell reverse shells and Meterpreter sessions. The module requires authentication (username/password or session cookie) and interacts with the SharePoint server over HTTP(S). The main endpoints of interest are the SharePoint base path (TARGETURI) and the web.config file. The code is operational and weaponized for use within the Metasploit framework.
Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.
Vendor-confirmed product mapping. Mallory continuously reconciles this list against your asset inventory.
2 sources tracked across advisories and community write-ups. News coverage will land here when it surfaces.
No news coverage yet. Advisories and community discussion only.
Query your assets running an affected version, and investigate the blast radius.
Every observed campaign linking this CVE to a named adversary.
Malware families riding this exploit, with evidence and IOCs.
YARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.
Cross-references every affected SKU, including bundled OEM variants.
Community discussion across Reddit, Mastodon, and other social sources.