# CVE-2022-50690: Wondershare MirrorGo 2.0.11.346 Local Privilege Escalation via Insecure File Permissions

> Local attackers can replace an executable with a malicious file to execute arbitrary code with LocalSystem privileges due to insecure file permissions.

- **Severity:** High 8.5 (`CVSS:4.0/AV:L/AC:L/AT:N/PR:L/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N`)
- **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:** 22 Dec 2025
- **Updated:** 22 Dec 2025
- **Also known as:** GHSA-jcf7-5pqw-fpmw

## What is CVE-2022-50690?

CVE-2022-50690 is a high-severity vulnerability in Wondershare MirrorGo, published on 22 Dec 2025. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

Wondershare MirrorGo 2.0.11.346 contains a local privilege escalation vulnerability due to incorrect file permissions on executable files. Unprivileged local users can replace the ElevationService.exe with a malicious file to execute arbitrary code with LocalSystem privileges.

Weakness: CWE-732 (Incorrect Permission Assignment for Critical Resource)

## Which versions are affected by CVE-2022-50690?


## How do I fix CVE-2022-50690?

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

## Is CVE-2022-50690 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2022-50690 and fix it if it is affected.

What it is: CVE-2022-50690 is a high-severity vulnerability in Wondershare MirrorGo, published on 22 Dec 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-2022-50690 in the wild and no public exploit code.

Affected product: Wondershare MirrorGo. 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-2022-50690/ (Markdown: https://insights.sbomify.com/CVE-2022-50690/index.md)
```

## Sources

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

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