# CVE-2026-50231: Lyrion Music Server 9.2.0 Unauthenticated Stored XSS via server.log

> Attackers can inject malicious scripts into the log viewer via unescaped parameters, leading to arbitrary script execution in users' browsers.

- **Severity:** Medium 5.1 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:P/VC:N/VI:N/VA:N/SC:L/SI:L/SA: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:** 5 Jun 2026
- **Updated:** 8 Jun 2026
- **Also known as:** GHSA-4hhv-5h2w-9qm2

## What is CVE-2026-50231?

CVE-2026-50231 is a medium-severity cross-site scripting vulnerability in LMS Community Lyrion Music Server, published on 5 Jun 2026. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link.

### Official description

Lyrion Music Server 9.2.0 contains an unauthenticated stored cross-site scripting vulnerability in the log viewer that allows attackers to inject malicious scripts by exploiting unescaped template variables. Attackers can inject XSS payloads through search, lines, and path query parameters or by crafting values that get logged such as URLs, User-Agent headers, stream titles, or player names to execute arbitrary scripts in users' browsers.

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

## Which versions are affected by CVE-2026-50231?


## How do I fix CVE-2026-50231?

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

## Is CVE-2026-50231 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-50231 and fix it if it is affected.

What it is: CVE-2026-50231 is a medium-severity cross-site scripting vulnerability in LMS Community Lyrion Music Server, published on 5 Jun 2026. 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-2026-50231 in the wild and no public exploit code.

Affected product: LMS Community Lyrion Music 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-2026-50231/ (Markdown: https://insights.sbomify.com/CVE-2026-50231/index.md)
```

## Sources

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

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