CVE-2020-1103 json
Microsoft SharePoint Information Disclosure Vulnerability
published 2020-05-21 6 y ago modified 2026-08-19 2 mo ago also EUVD-2020-11991
- cvss
- 6.5
- version 3.1, NVD
- 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
An information disclosure vulnerability exists where certain modes of the search function in Microsoft SharePoint Server are vulnerable to cross-site search attacks (a variant of cross-site request forgery, CSRF). When users are simultaneously logged in to Microsoft SharePoint Server and visit a malicious web page, the attacker can, through standard browser functionality, induce the browser to invoke search queries as the logged in user. While the attacker can’t access the search results or documents as such, the attacker can determine whether the query did return results or not, and thus by issuing targeted queries discover facts about documents that are searchable for the logged-in user. The security update addresses the vulnerability by running the search queries in a way that doesn’t expose them to this browser vulnerability.
Patch / fix
Exploit prediction
2.21% 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 |
|---|---|---|---|
| NVD | 3.1 | 6.5 | CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:N/A:N |
| NVD | 2.0 | 4.3 | AV:N/AC:M/Au:N/C:P/I:N/A:N |
Affected products
- Microsoft Microsoft SharePoint Enterprise Server 2016
- Microsoft Microsoft SharePoint Foundation 2013 Service Pack 1
- Microsoft Microsoft SharePoint Server 2019
Classification
- Weakness
-
- CWE-352 Cross-Site Request Forgery
References
-
msrc.microsoft.com
/update-guide/vulnerability/CVE-2020-1103
vendor-advisory, patch
-
portal.msrc.microsoft.com
/en-US/security-guidance/advisory/CVE-2020-1103
patch, vendor-advisory
Sources
- CVE List CVE-2020-1103
- NVD CVE-2020-1103
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.