# CVE-2025-65229: Cross-site scripting in n/a

> An authenticated user can inject malicious scripts via the Player name field, which execute in other users' browsers when viewing player information.

- **Severity:** Medium 4.6 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:U/C:L/I:L/A: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:** 8 Dec 2025
- **Updated:** 20 Jan 2026
- **Also known as:** GHSA-m9rv-g47r-qvh2

## What is CVE-2025-65229?

CVE-2025-65229 is a medium-severity cross-site scripting vulnerability in n/a, published on 8 Dec 2025. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link.

### Official description

A stored cross-site scripting (XSS) vulnerability exists in the web interface of Lyrion Music Server <= 9.0.3. An authenticated user with access to Settings Player can save arbitrary HTML/JavaScript in the Player name field. That value is stored by the server and later rendered without proper output encoding on the Information (Player Info) tab, causing the script to execute in the context of any user viewing that page.

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

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

It affects 1 product.


Products: Lyrion Lyrion Music Server.

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

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

## Is CVE-2025-65229 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2025-65229 is a medium-severity cross-site scripting vulnerability in n/a, published on 8 Dec 2025. 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-2025-65229 in the wild and no public exploit code.

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

## Sources

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

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