# CVE-2019-1033: Microsoft Office SharePoint XSS Vulnerability

> An authenticated attacker can execute arbitrary scripts in the victim's browser to read unauthorized data and perform actions on their behalf.

- **Severity:** Medium 5.4 (`CVSS:3.0/AV:N/AC:L/PR:L/UI:R/S:C/C:L/I:L/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 12 Jun 2019
- **Updated:** 20 May 2025
- **Also known as:** GHSA-gp38-6cc3-gxr4

## What is CVE-2019-1033?

CVE-2019-1033 is a medium-severity cross-site scripting vulnerability in Microsoft Sharepoint Enterprise Server, published on 12 Jun 2019. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link.

### Official description

A cross-site-scripting (XSS) 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. The 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.

Weakness: CWE-79 (Improper Neutralization of Input During Web Page Generation)

## Which versions are affected by CVE-2019-1033?

It affects 4 products.


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

## How do I fix CVE-2019-1033?

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

## Is CVE-2019-1033 being exploited?

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

## Other vulnerabilities in Microsoft Sharepoint Enterprise Server

- [CVE-2018-0909](https://insights.sbomify.com/CVE-2018-0909/): Cross-site scripting in Microsoft SharePoint (high 8.8)
- [CVE-2018-0910](https://insights.sbomify.com/CVE-2018-0910/): Cross-site scripting in Microsoft SharePoint (high 8.8)
- [CVE-2018-0911](https://insights.sbomify.com/CVE-2018-0911/): Cross-site scripting in Microsoft SharePoint (high 8.8)
- [CVE-2018-0912](https://insights.sbomify.com/CVE-2018-0912/): Cross-site scripting in Microsoft SharePoint (high 8.8)
- [CVE-2018-0913](https://insights.sbomify.com/CVE-2018-0913/): Cross-site scripting in Microsoft SharePoint (high 8.8)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2019-1033 and fix it if it is affected.

What it is: CVE-2019-1033 is a medium-severity cross-site scripting vulnerability in Microsoft Sharepoint Enterprise Server, published on 12 Jun 2019. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2019-1033 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-2019-1033/ (Markdown: https://insights.sbomify.com/CVE-2019-1033/index.md)
```

## Sources

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

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