dbcve.org
Cross-site Scripting (XSS)Weakness · CWE-79

CVE-2026-50231

HIGH · 7.2 CVSS v3.1 Published 2026-06-05
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
81/100
Remediation priority · High
Remotely reachable No privileges Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
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.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

Lyrion Music Server 9.2.0 contains an unauthenticated stored cross-site scripting vulnerability in the log viewer. Attackers can inject malicious scripts through unsanitized query parameters (search, lines, path) or by crafting values like URLs, User-Agent headers, stream titles, or player names that get logged and displayed without output encoding, allowing arbitrary JavaScript execution in victim browsers.

MitigationApply output encoding to all user-controlled data rendered in the log viewer and implement input validation for query parameters. Deploy Content Security Policy (CSP) headers as defense-in-depth to mitigate XSS impact.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
User interaction
None
Scope
Changed
Confidentiality
Low
Integrity
Low
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:L/I:L/A:N

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Confirm Lyrion Music Server is installed
    Check for the application in standard installation directories or look for the service process running (common paths: /opt/lyrion/, C:\Program Files\Lyrion\, or check running services for 'Lyrion' or 'squeezebox' processes)
    Affected if The application is present and running on the system
  2. Verify the installed version is 9.2.0
    Check the version via the administrative web interface (usually in Help > About or Settings > System), or check the executable/service version information
    Affected if The installed version is exactly 9.2.0 or falls within the affected range around this release
  3. Confirm the log viewer feature is accessible
    Locate the log viewer interface in the web admin panel (typically under Settings > Logging, Diagnostics, or Server > Log Files)
    Affected if The log viewer web interface is enabled and accessible without authentication or with admin credentials
  4. Test for unsanitized query parameter injection
    Access the log viewer URL with crafted query parameters such as: /logviewer?search=<script>alert(1)</script> or /logviewer?lines=100&path=<img src=x onerror=alert(1)> and inspect if the values are rendered without encoding
    Affected if The injected script tags or HTML/JS payloads execute or render unescaped in the log viewer output
  5. Verify logged data displays without output encoding
    Trigger logging of user-controlled values: inject a test payload (e.g., a custom User-Agent header, stream title, or player name containing <script>test</script>), then access the log viewer and check if these values appear with the tags intact and executable
    Affected if User-supplied data appears in the log viewer output with raw HTML/JavaScript tags visible and executable

A user is affected if they are running Lyrion Music Server version 9.2.0 with the log viewer feature accessible and user-controllable data (query parameters, User-Agent, stream titles, or player names) appearing unencoded in the log output.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

From vendor data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Apply output encoding to all user-controlled data rendered in the log viewer and implement input validation for query parameters. Deploy Content Security Policy (CSP) headers as defense-in-depth to mitigate XSS impact.

Have this fixed Scoped from the published advisory
  • Consultation4.0 h
  • Implementation12.0 h
  • Testing6.0 h
  • Review / QA3.0 h
25.0 hours of engineering $4,400
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $7,040.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-50231 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-50231 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data