CVE-2026-50235
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 a reflected cross-site scripting vulnerability in advanced search parameters that fail to properly sanitize user input before displaying it in search forms. Attackers can inject malicious scripts through unfiltered search parameters to execute arbitrary JavaScript in users' browsers and steal session information.
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 is vulnerable to reflected cross-site scripting (XSS) in its advanced search functionality. The application fails to sanitize user-supplied input in search parameters before reflecting them back in the search form's HTML output. An attacker can craft malicious search queries containing JavaScript payload that will execute in the context of any user viewing the search results, potentially allowing session cookie theft and credential harvesting.
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 installation and versionCheck the installed version of Lyrion Music Server. This is typically available via the application web interface (often in Help > About), command-line interface, or package manager depending on installation method.Affected if The installed version is 9.2.0
-
Locate the advanced search functionalityAccess the web interface and navigate to or identify the advanced search feature. This is typically found in the search or library section of the application.Affected if The advanced search functionality is accessible and enabled in the environment
-
Test for reflected input in search parametersSubmit a benign test string (such as <script>alert(1)</script> or a harmless HTML tag) in one or more advanced search fields, then inspect the HTTP response and the search results page HTML to see if the input is reflected without proper encoding.Affected if The search parameter values are returned in the response HTML without encoding or sanitization (the test payload appears literally in the page source)
A user is affected if they are running Lyrion Music Server version 9.2.0 with the advanced search feature enabled and search parameters are reflected unencoded in the HTML response.
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 dataImplement proper input validation and context-aware output encoding for all search parameters before rendering in HTML. Additionally, deploy Content Security Policy (CSP) headers to mitigate XSS execution.
- Consultation3.0 h
- Implementation6.0 h
- Testing3.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,984.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-50235 — 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-50235 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