# CVE-2025-27743: Microsoft System Center Elevation of Privilege Vulnerability

> An authorized local attacker can elevate privileges via an untrusted search path in Microsoft System Center components.

- **Severity:** High 7.8 (`CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H/E:U/RL:O/RC:C`)
- **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:** 8 Apr 2025
- **Updated:** 10 Aug 2026
- **Also known as:** GHSA-6vg9-pg49-5fg4

## What is CVE-2025-27743?

CVE-2025-27743 is a high-severity vulnerability in Microsoft System Center Data Protection Manager 2019, published on 8 Apr 2025. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

Untrusted search path in System Center allows an authorized attacker to elevate privileges locally.

Weakness: CWE-426 (Untrusted Search Path)

## Which versions are affected by CVE-2025-27743?

It affects 5 products.


Products: Microsoft System Center Data Protection Manager, Microsoft System Center Operations Manager, Microsoft System Center Orchestrator, Microsoft System Center Service Manager, Microsoft System Center Virtual Machine Manager.

## How do I fix CVE-2025-27743?

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

## Is CVE-2025-27743 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2025-27743 and fix it if it is affected.

What it is: CVE-2025-27743 is a high-severity vulnerability in Microsoft System Center Data Protection Manager 2019, published on 8 Apr 2025. 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-2025-27743 in the wild and no public exploit code.

Affected product: Microsoft System Center Data Protection Manager 2019. 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-2025-27743/ (Markdown: https://insights.sbomify.com/CVE-2025-27743/index.md)
```

## Sources

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

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