CVE-2020-1452 json
Microsoft SharePoint Remote Code Execution Vulnerability
published 2020-09-11 6 y ago modified 2026-06-17 4 mo ago also EUVD-2020-12327
- cvss
- 8.6
- version 3.1, CNA
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 2.2%
- EPSS 2.2% chance of exploitation in 30 days, percentile 82%
- public exploits
- 0
- none known
Summary
<p>A remote code execution vulnerability exists in Microsoft SharePoint when the software fails to check the source markup of an application package. An attacker who successfully exploited the vulnerability could run arbitrary code in the context of the SharePoint application pool and the SharePoint server farm account.</p> <p>Exploitation of this vulnerability requires that a user uploads a specially crafted SharePoint application package to an affected version of SharePoint.</p> <p>The security update addresses the vulnerability by correcting how SharePoint checks the source markup of application packages.</p>
Patch / fix
CISA SSVC
- Exploitation
- none
- Automatable
- yes
- Technical impact
- partial
- Assessed
- 23 mo ago
Exploit prediction
2.15% chance of exploitation in the next 30 days, higher than 82% of all scored CVEs (FIRST EPSS, 2026-11-08).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| CNA | 3.1 | 8.6 | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:H/A:L/E:P/RL:O/RC:C |
| CNA | 3.1 | 8.6 | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:H/A:L |
| NVD | 2.0 | 7.5 | AV:N/AC:L/Au:N/C:P/I:P/A:P |
Affected products
- Microsoft Microsoft SharePoint Enterprise Server 2016
- Microsoft Microsoft SharePoint Enterprise Server 2013 Service Pack 1
- Microsoft Microsoft SharePoint Server 2019
- Microsoft Microsoft SharePoint Foundation 2010 Service Pack 2
- Microsoft Microsoft SharePoint Foundation 2013 Service Pack 1
Classification
- Weakness
-
- CWE-494 Download of Code Without Integrity Check
References
-
portal.msrc.microsoft.com
/en-US/security-guidance/advisory/CVE-2020-1452
patch, vendor-advisory
Sources
- CVE List CVE-2020-1452
- NVD CVE-2020-1452
Fencer Vulns keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.