# CVE-2025-53095: Sunshine application-wide CSRF in the UI leads to command injection as Administrator

> Attackers can exploit CSRF in Sunshine's web UI to inject arbitrary commands executed with Administrator privileges via the Command Preparations feature.

- **Severity:** Critical 9.7 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:H/I:H/A:H`)
- **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:** 1 Jul 2025
- **Updated:** 1 Jul 2025
- **Also known as:** GHSA-39hj-fxvw-758m

## What is CVE-2025-53095?

CVE-2025-53095 is a critical vulnerability in LizardByte Sunshine, published on 1 Jul 2025. 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

Sunshine is a self-hosted game stream host for Moonlight. Prior to version 2025.628.4510, the web UI of Sunshine lacks protection against Cross-Site Request Forgery (CSRF) attacks. This vulnerability allows an attacker to craft a malicious web page that, when visited by an authenticated user, can trigger unintended actions within the Sunshine application on behalf of that user. Specifically, since the application does OS command execution by design, this issue can be exploited to abuse the "Command Preparations" feature, enabling an attacker to inject arbitrary commands that will be executed with Administrator privileges when an application is launched. This issue has been patched in version 2025.628.4510.

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

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

It affects 1 product.


Products: Lizardbyte Sunshine.

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

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

## Is CVE-2025-53095 being exploited?

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

## Other vulnerabilities in LizardByte Sunshine

- [CVE-2026-32253](https://insights.sbomify.com/CVE-2026-32253/): Sunshine: Authentication bypass via improper client certificate validation (critical 9.8)
- [CVE-2025-10198](https://insights.sbomify.com/CVE-2025-10198/): LizardBytes Sunshine for Windows contains a DLL search-order hijacking vulnerability (high 7.8)
- [CVE-2025-10199](https://insights.sbomify.com/CVE-2025-10199/): A local privilege escalation vulnerability exists in LizardBytes' Sunshine for Windows (high 7.8)
- [CVE-2024-51738](https://insights.sbomify.com/CVE-2024-51738/): Sunshine improperly enforces pairing protocol request order (high 7.7)
- [CVE-2024-31220](https://insights.sbomify.com/CVE-2024-31220/): Sunshine vulnerable to remote unauthenticated arbitrary file read (high 7.3)

## Fix prompt for AI coding agents

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

What it is: CVE-2025-53095 is a critical vulnerability in LizardByte Sunshine, published on 1 Jul 2025. 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-2025-53095 in the wild and no public exploit code.

Affected product: LizardByte Sunshine. 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-53095/ (Markdown: https://insights.sbomify.com/CVE-2025-53095/index.md)
```

## Sources

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

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