CVE-2026-50232
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 stored cross-site scripting vulnerability that allows attackers to inject malicious scripts through media file metadata tags like GENRE, ARTIST, and ALBUM. Attackers can craft files with XSS payloads in metadata tags that execute in the web interface when users view track information or play files, enabling access to management functions and settings disclosure.
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 fails to sanitize metadata fields (GENRE, ARTIST, ALBUM) when parsing media files, allowing stored XSS payloads to persist in the database. When users view track information or play affected files through the web interface, the malicious script executes, potentially exposing session tokens or management function access.
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 checksWork through these to decide whether this CVE applies to you.
-
Verify Lyrion Music Server versionCheck the installed version of Lyrion Music Server (typically via server status page, command line version flag, or about section in the web interface) and confirm it is version 9.2.0Affected if The installed version is 9.2.0 exactly
-
Identify media file imports with metadata parsingReview import logs or activity records to confirm that media files containing GENRE, ARTIST, and ALBUM metadata fields are being ingested into the serverAffected if Media files with metadata are being imported into the system
-
Inspect database metadata fields for script contentQuery the database (or use server export functionality) to examine stored values in GENRE, ARTIST, and ALBUM fields for any HTML or JavaScript patterns such as <script>, javascript:, onload, onerror, or other script execution indicatorsAffected if Any records contain unsanitized script tags or event handlers in metadata fields
-
Confirm web interface is accessible and usedVerify that the Lyrion web interface is enabled and accessible, as this is required for the XSS to trigger when users view track information or play filesAffected if The web interface is enabled and users can view track details or play media through it
A user is affected if running version 9.2.0, media files with metadata have been imported, the database contains unsanitized script content in GENRE/ARTIST/ALBUM fields, and the web interface is accessible for viewing or playback.
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 strict input validation and output encoding for all media metadata fields at the point of ingestion and display to prevent script execution.
- Consultation3.0 h
- Implementation8.0 h
- Testing4.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 $4,800.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-50232 — 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-50232 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