CVE-2020-1105 json
Microsoft SharePoint Spoofing Vulnerability
published 2020-05-21 6 y ago modified 2026-08-19 2 mo ago also EUVD-2020-11993
- cvss
- 5.4
- version 3.1, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 1.6%
- EPSS 1.6% chance of exploitation in 30 days, percentile 75%
- public exploits
- 0
- none known
Summary
A spoofing vulnerability exists when Microsoft SharePoint Server does not properly sanitize a specially crafted web request to an affected SharePoint server. An authenticated attacker could exploit the vulnerability by sending a specially crafted request to an affected SharePoint server. The attacker who successfully exploited the vulnerability could then perform cross-site scripting attacks on affected systems and run script in the security context of the current user. These attacks could allow the attacker to read content that the attacker is not authorized to read, use the victim's identity to take actions on the SharePoint site on behalf of the user, such as change permissions and delete content, and inject malicious content in the browser of the user. The security update addresses the vulnerability by helping to ensure that SharePoint Server properly sanitizes web requests.
Patch / fix
Exploit prediction
1.57% chance of exploitation in the next 30 days, higher than 75% of all scored CVEs (FIRST EPSS, 2026-11-08).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| NVD | 3.1 | 5.4 | CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:C/C:L/I:L/A:N |
| NVD | 2.0 | 3.5 | AV:N/AC:M/Au:S/C:N/I:P/A:N |
Affected products
- Microsoft Microsoft SharePoint Enterprise Server 2016
- Microsoft Microsoft SharePoint Foundation 2013 Service Pack 1
Classification
- Weakness
-
- CWE-79 Improper Neutralization of Input During Web Page Generation
References
-
msrc.microsoft.com
/update-guide/vulnerability/CVE-2020-1105
vendor-advisory, patch
-
portal.msrc.microsoft.com
/en-US/security-guidance/advisory/CVE-2020-1105
patch, vendor-advisory
Sources
- CVE List CVE-2020-1105
- NVD CVE-2020-1105
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.