# CVE-2020-1103: Microsoft SharePoint Information Disclosure Vulnerability

> Attackers can exploit cross-site search flaws in SharePoint to infer document existence for logged-in users via malicious web pages.

- **Severity:** Medium 6.5 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 21 May 2020
- **Updated:** 19 Aug 2026
- **Also known as:** GHSA-88wv-c32x-w3h7

## What is CVE-2020-1103?

CVE-2020-1103 is a medium-severity vulnerability in Microsoft Sharepoint Enterprise Server, published on 21 May 2020. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.

### Official description

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.

Weakness: CWE-352 (Cross-Site Request Forgery)

## Which versions are affected by CVE-2020-1103?

It affects 3 products.


Products: Microsoft Sharepoint Enterprise Server, Microsoft Sharepoint Foundation, Microsoft Sharepoint Server.

## How do I fix CVE-2020-1103?

No fix has been published for CVE-2020-1103 yet. Limit exposure of the affected software until one is available.

## Is CVE-2020-1103 being exploited?

There is no known exploitation of CVE-2020-1103 in the wild and no public exploit code.

## Other vulnerabilities in Microsoft Sharepoint Enterprise Server

- [CVE-2019-0604](https://insights.sbomify.com/CVE-2019-0604/): Microsoft SharePoint Remote Code Execution (critical 9.8, exploited in the wild)
- [CVE-2023-24955](https://insights.sbomify.com/CVE-2023-24955/): Microsoft SharePoint Server Code Injection (high 7.2, exploited in the wild)
- [CVE-2025-49706](https://insights.sbomify.com/CVE-2025-49706/): Microsoft SharePoint Improper Authentication (medium 6.5, exploited in the wild)
- [CVE-2020-1210](https://insights.sbomify.com/CVE-2020-1210/): Microsoft SharePoint Remote Code Execution Vulnerability (critical 9.9)
- [CVE-2020-1595](https://insights.sbomify.com/CVE-2020-1595/): Microsoft SharePoint Remote Code Execution Vulnerability (critical 9.9)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2020-1103 and fix it if it is affected.

What it is: CVE-2020-1103 is a medium-severity vulnerability in Microsoft Sharepoint Enterprise Server, published on 21 May 2020. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2020-1103 in the wild and no public exploit code.

Affected product: Microsoft Sharepoint Enterprise Server. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2020-1103/ (Markdown: https://insights.sbomify.com/CVE-2020-1103/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2020-1103
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2020-1103
- OSV: https://osv.dev/vulnerability/CVE-2020-1103

---
From sbomify Insights: https://insights.sbomify.com/CVE-2020-1103/
Summaries are generated and may contain mistakes; the official description above is the record.