CVE-2026-50230
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 · uneditedLyrion Music Server 9.2.0 contains an unauthenticated reflected cross-site scripting vulnerability in the server.log endpoint that allows attackers to inject arbitrary HTML and JavaScript code through the search parameter. Attackers can craft malicious URLs with JavaScript payloads in the search parameter to execute code in users' browsers within the context of the affected application.
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 confidenceLyrion Music Server 9.2.0 has a reflected cross-site scripting (XSS) vulnerability in the server.log endpoint. The search parameter is not properly sanitized, allowing attackers to inject arbitrary HTML and JavaScript code via malicious URLs. Since the vulnerability is unauthenticated and reflected, successful exploitation requires tricking users into clicking crafted links.
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
- Required
- Scope
- Changed
- Confidentiality
- Low
- Integrity
- Low
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/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 checksWork through these to decide whether this CVE applies to you.
-
Identify Lyrion Music Server versionCheck the installed version of Lyrion Music Server (typically available via the web interface footer, about page, or server status endpoint)Affected if Version is 9.2.0 or if the server.log endpoint is present and accessible
-
Verify server.log endpoint accessibilityAttempt to access the /server.log endpoint on the Lyrion Music Server (e.g., https://<host>/server.log or similar path)Affected if The endpoint responds and accepts a search parameter
-
Test search parameter for reflected inputSend a request to the server.log endpoint with a test value in the search parameter (e.g., ?search=test123) and inspect the response to see if the value is reflected in the outputAffected if The search parameter value is reflected in the response without encoding or sanitization
-
Check for input validation on search parameterExamine the application response when special characters are included in the search parameter (e.g., <script>alert(1)</script>)Affected if Special characters are reflected as-is in the response, indicating lack of input validation and output encoding
A user is affected if they are running Lyrion Music Server version 9.2.0 with the server.log endpoint accessible and the search parameter reflects user input without proper encoding or validation.
Generated from the published advisory. Verify against your own configuration.
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 dataApply proper output encoding and input validation to the search parameter in the server.log endpoint to neutralize malicious payloads. Consider implementing a Content Security Policy (CSP) as an additional defense layer.
- Consultation2.0 h
- Implementation4.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,560.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-50230 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2026-50230 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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