Skip to content
skopnix

CVE-2020-1147 · Published 14 Jul 2020

Microsoft .NET Framework, SharePoint, Visual Studio

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

Microsoft .NET Framework, Microsoft SharePoint, and Visual Studio contain a remote code execution vulnerability when the software fails to check the source markup of XML file input. Successful exploitation allows an attacker to execute code in the context of the process responsible for deserialization of the XML content.

CISA required action (federal due date 3 May 2022): Apply updates per vendor instructions.

Signals

KEV, exploited in the wild
yes, added 3 Nov 2021, due 3 May 2022
EPSS, 30-day forecast
96%, 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 14 Jul 2020 to today

443 days from the first proof of concept to the KEV listing
2023202420252026Disclosed 14 Jul 2020Metasploit 29 Jul 2020First PoC 17 Aug 2020KEV 3 Nov 2021today
  1. Disclosed
  2. Metasploit+15 d
  3. First PoC+19 d
  4. KEV+443 d

443 days from the first proof of concept to the KEV listing

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 0Metasploit 1Exploit-DB 2

Metasploit1

  1. A remotely exploitable vulnerability exists within SharePoint that can be leveraged by a remote authenticated attacker to execute code within the context of the SharePoint application service. The privileges in this execution context are determined by the account that is specified when SharePoint is installed and configured. The vulnerability is related to a failure to validate the source of XML input data, leading to an unsafe deserialization operation th

    ruby · first seen by skopnix 18 Oct 2026

Exploit-DB2

  1. created 17 Aug 2020

  2. created 23 Jul 2021

References

Watch this one?

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

Telegram ↗KEV RSSAPIStack check