CVE-2020-1147
A remote code execution vulnerability exists in .NET Framework, Microsoft SharePoint, and Visual Studio when the software fails to check the source markup of XML file input, aka '.NET Framework, SharePoint Server, and Visual Studio Remote Code Execution Vulnerability'.
- CVSS
- 7.8Highscored by CISA
- Exploited in the wild
- Yes, in CISA KEV since 3 Nov 2021CISA deadline for US federal agencies: 3 May 2022public exploit code
- EPSS
- 95.8%chance of exploitation in the next 30 daystop 0.2% of scored CVEsFIRST score of 11 Nov 2026
- Fix
- Patch availablesee the advisories in the references
- Published
- 14 Jul 2020analysed here 12 Nov 2026
Do first. Apply updates per vendor instructions. (CISA's required action for this KEV entry)
Summary
Triage
- Exploitable
- At runtime
- Attack vector
- local
- Can a WAF block it?
- No. See why
The summary, impact and action text on this page are written by our AI analysis pipeline, or taken from the NVD description when a CVE was imported from NVD. They are not the vendor's wording: check them against the sources. A longer AI executive summary and technical analysis are generated for signed-in accounts on the Max plan.
Affected products
| Product | Affected versions | Vendor says fixed in |
|---|---|---|
| Microsoft Microsoft .NET Framework 2.0 | Service Pack 2 on Windows Server 2008 for 32-bit Systems Service Pack 2Service Pack 2 on Windows Server 2008 for x64-based Systems Service Pack 2Vendor says fixed in: not stated | |
| Microsoft Microsoft .NET Framework 3.0 | Service Pack 2 on Windows Server 2008 for 32-bit Systems Service Pack 2Service Pack 2 on Windows Server 2008 for x64-based Systems Service Pack 2Vendor says fixed in: not stated | |
| Microsoft Microsoft .NET Framework 3.5 | Windows 8.1 for 32-bit systemsWindows 8.1 for x64-based systemsWindows Server 2012Windows Server 2012 (Server Core installation)Windows Server 2012 R2Windows Server 2012 R2 (Server Core installation)Vendor says fixed in: not stated | |
| Microsoft Microsoft .NET Framework 3.5.1 | Windows 7 for 32-bit Systems Service Pack 1Windows 7 for x64-based Systems Service Pack 1Windows Server 2008 R2 for x64-based Systems Service Pack 1Vendor says fixed in: not stated | |
| Microsoft Microsoft .NET Framework 3.5 AND 4.8 on Windows Server, version 1903 (Server Core installation) | 1903Vendor says fixed in: not stated | |
| Microsoft Microsoft .NET Framework 4.5.2 | Windows 7 for 32-bit Systems Service Pack 1Windows 7 for x64-based Systems Service Pack 1Windows 8.1 for 32-bit systemsWindows 8.1 for x64-based systemsWindows RT 8.1Windows Server 2008 for 32-bit Systems Service Pack 2Windows Server 2008 for x64-based Systems Service Pack 2Windows Server 2008 R2 for x64-based Systems Service Pack 1Windows Server 2008 R2 for x64-based Systems Service Pack 1 (Server Core installation)Windows Server 2012Windows Server 2012 (Server Core installation)Windows Server 2012 R2Windows Server 2012 R2 (Server Core installation)Vendor says fixed in: not stated | |
| Microsoft Microsoft .NET Framework 4.6 | Windows Server 2008 for 32-bit Systems Service Pack 2Windows Server 2008 for x64-based Systems Service Pack 2Vendor says fixed in: not stated | |
| Microsoft Microsoft .NET Framework 4.6/4.6.1/4.6.2/4.7/4.7.1/4.7.2 | Windows 7 for 32-bit Systems Service Pack 1Windows 7 for x64-based Systems Service Pack 1Windows 8.1 for 32-bit systemsWindows 8.1 for x64-based systemsWindows RT 8.1Windows Server 2008 R2 for x64-based Systems Service Pack 1Windows Server 2008 R2 for x64-based Systems Service Pack 1 (Server Core installation)Windows Server 2012Windows Server 2012 (Server Core installation)Windows Server 2012 R2Windows Server 2012 R2 (Server Core installation)Vendor says fixed in: not stated | |
| Microsoft Microsoft SharePoint Enterprise Server | 20162013 Service Pack 1Vendor says fixed in: not stated | |
| Microsoft Microsoft SharePoint Server | 20192010 Service Pack 2Vendor says fixed in: not stated | |
| Microsoft Microsoft Visual Studio 2019 | 16.0Vendor says fixed in: not stated | |
| Microsoft .NET Core | 2.13.1Vendor says fixed in: not stated |
As published in the CVE Program record. A version outside these ranges is not a statement that it is unaffected — vendors sometimes understate a range, and distribution-backported builds carry upstream numbers that do not reflect what was patched into them.
Products named in our analysis
- microsoft:.net_core
- microsoft:.net_framework
- microsoft:sharepoint_enterprise_server
- microsoft:sharepoint_server
- microsoft:visual_studio_2017
- microsoft:visual_studio_2019
Fix and mitigation
WAF and other mitigations
Can a WAF block it? No. The attack needs local access to the machine, so a WAF is not on its path.
Also consider: patch
Based on the attack vector (local or physical access). We check Cloudflare, AWS, Google Cloud Armor and Azure; for Akamai, Imperva, Fastly, F5, ask your vendor.
Remediation steps (AI-written)
Step-by-step remediation is generated for accounts on the Max plan, for CVEs that match a technology in their stack. Add this technology to your stack to see the fix checklist.
Exploitation evidence
- CISA KEV catalog
- Listed since 3 Nov 2021.
- CISA due date
- 3 May 2022, the remediation deadline for US federal agencies
- CISA required action
- Apply updates per vendor instructions.
- Public exploit code
- Yes: 2 on Exploit-DB · 1 Metasploit module
- CISA SSVC
- exploitation active, automatable no, technical impact totalAssessed by CISA 4 Feb 2025 (SSVC 2.0.3). Exploitation is none, poc (public proof of concept) or active.
Exploit-DB
- Microsoft SharePoint Server 2019 - Remote Code Execution (2)webapps, 23 Jul 2021
- Microsoft SharePoint Server 2019 - Remote Code Executionwebapps, 17 Aug 2020
Metasploit
- exploit/windows/http/sharepoint_data_deserializationexploit, rank excellent
Listed so you can judge urgency, not as a recommendation to run anything. GitHub “proofs of concept” are unvetted: some are fake or carry malware. Exploit-DB marks the entries its staff verified.
Timeline
- 14 Jul 2020Published
- 17 Aug 2020First public exploit or proof of concept33 days later
- 3 Nov 2021Added to CISA KEV (exploited in the wild)443 days (about 1 year) later
- 3 May 2022CISA remediation due date (US federal agencies)181 days (about 6 months) later
- 4 Feb 2025CISA SSVC assessment: exploitation active1,009 days (about 3 years) later
- 21 Oct 2025CVE record last updated259 days (about 9 months) later
- 12 Nov 2026Analysed by vulneraibility.com387 days (about 1 year) later
CVSS vector
CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H
| Metric | Value | What it means |
|---|---|---|
| Attack vector | LocalLocal access required (shell, logged-in user). | Local access required (shell, logged-in user). |
| Attack complexity | LowRepeatable attack, no special conditions. | Repeatable attack, no special conditions. |
| Privileges required | NoneThe attacker needs no prior access. | The attacker needs no prior access. |
| User interaction | RequiredA victim must click, open or otherwise cooperate. | A victim must click, open or otherwise cooperate. |
| Scope | UnchangedImpact stays within the vulnerable component. | Impact stays within the vulnerable component. |
| Confidentiality | HighTotal data disclosure possible. | Total data disclosure possible. |
| Integrity | HighComplete modification possible. | Complete modification possible. |
| Availability | HighFull outage possible. | Full outage possible. |
Common questions
Is CVE-2020-1147 being exploited?
Yes. CVE-2020-1147 appears in CISA's Known Exploited Vulnerabilities catalog, which means exploitation in the wild has been confirmed and reported. Treat it as active rather than theoretical, and patch it ahead of higher-scoring vulnerabilities that carry no exploitation evidence.
How severe is CVE-2020-1147?
CVE-2020-1147 is rated High with a CVSS score of 7.8. Severity describes how bad exploitation would be, not how likely it is: pair it with exploitation evidence before deciding what to patch first.
Is there a patch for CVE-2020-1147?
Yes. A fix has been recorded for CVE-2020-1147. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.
What does CVE-2020-1147 affect?
CVE-2020-1147 affects microsoft:.net_core, microsoft:.net_framework, microsoft:sharepoint_enterprise_server, microsoft:sharepoint_server, and 2 further products or versions. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.
Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.
References
6 references in the CVE record, grouped by the tags the record gives them.
Other links (6)
- portal.msrc.microsoft.com /en-US/security-guidance/advisory/CVE-2020-1147
- packetstormsecurity.com /files/158694/SharePoint-DataSet-DataTable-Deserialization.html
- packetstormsecurity.com /files/158876/Microsoft-SharePoint-Server-2019-Remote-Code-Execution.html
- exploitalert.com /view-details.html?id=35992
- packetstormsecurity.com /files/163644/Microsoft-SharePoint-Server-2019-Remote-Code-Execution.html
- cisa.gov /known-exploited-vulnerabilities-catalog?field_cve=CVE-2020-1147
Where the data on this page comes from
- CVE List (CVE.org): description, affected versions, references; CVE Terms of Use
- NVD: CVSS and CPE data
- CISA KEV catalog: exploitation, date added, due date
- CISA Vulnrichment (ADP): SSVC decision points
- FIRST EPSS: exploit probability and percentile
- Exploit-DB: published exploits
- Metasploit Framework: exploit and scanner modules
Summary, impact and triage tags: written by our AI analysis pipeline from the sources above. Check them against the sources.
Similar CVEs
Get CVEs like this by email. Join the free digest: the CVEs we flag as major, all CVSS 8.0 or higher, in up to three emails a day (sent at 05:00, 11:00 and 15:00 UTC). Matching alerts to the products you run needs an account, and accounts are invite-only during the beta.