# CVE-2019-0727: Privilege escalation in Microsoft Visual Studio

> An attacker with local access can exploit arbitrary file deletion in Visual Studio collectors to escalate privileges.

- **Severity:** High 7.8 (`CVSS:3.0/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 16 May 2019
- **Updated:** 4 Aug 2024
- **Also known as:** GHSA-4vgf-c8vc-m3fj

## What is CVE-2019-0727?

CVE-2019-0727 is a high-severity vulnerability in Microsoft Visual Studio, published on 16 May 2019. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

An elevation of privilege vulnerability exists when the Diagnostics Hub Standard Collector or the Visual Studio Standard Collector allows file deletion in arbitrary locations.To exploit the vulnerability, an attacker would first have to log on to the system, aka 'Diagnostic Hub Standard Collector, Visual Studio Standard Collector Elevation of Privilege Vulnerability'.

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

It affects 6 products.


Products: Microsoft Visual Studio, Microsoft Visual Studio 2017, Microsoft Visual Studio 2019, Microsoft Windows 10, Microsoft Windows Server 2016, Microsoft Windows Server 2019.

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

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

## Is CVE-2019-0727 being exploited?

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

## Other vulnerabilities in Microsoft Visual Studio

- [CVE-2025-49739](https://insights.sbomify.com/CVE-2025-49739/): Visual Studio Elevation of Privilege Vulnerability (high 8.8)
- [CVE-2022-35777](https://insights.sbomify.com/CVE-2022-35777/): Visual Studio Remote Code Execution Vulnerability (high 8.8)
- [CVE-2022-35825](https://insights.sbomify.com/CVE-2022-35825/): Visual Studio Remote Code Execution Vulnerability (high 8.8)
- [CVE-2022-35826](https://insights.sbomify.com/CVE-2022-35826/): Visual Studio Remote Code Execution Vulnerability (high 8.8)
- [CVE-2022-35827](https://insights.sbomify.com/CVE-2022-35827/): Visual Studio Remote Code Execution Vulnerability (high 8.8)

## Fix prompt for AI coding agents

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

What it is: CVE-2019-0727 is a high-severity vulnerability in Microsoft Visual Studio, published on 16 May 2019. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2019-0727 in the wild and no public exploit code.

Affected product: Microsoft Visual Studio. 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-0727/ (Markdown: https://insights.sbomify.com/CVE-2019-0727/index.md)
```

## Sources

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

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