CVE-2026-50230
Unauthenticated Reflected XSS in Lyrion Music Server
Publication date: 2026-06-05
Last updated on: 2026-06-05
Assigner: VulnCheck
Description
Description
CVSS Scores
EPSS Scores
| Probability: | |
| Percentile: |
Meta Information
Affected Vendors & Products
| Vendor | Product | Version / Range |
|---|---|---|
| lyrion | music_server | to 9.2.0 (exc) |
Helpful Resources
Exploitability
| CWE ID | Description |
|---|---|
| CWE-79 | The product does not neutralize or incorrectly neutralizes user-controllable input before it is placed in output that is used as a web page that is served to other users. |
Attack-Flow Graph
AI Powered Q&A
Can you explain this vulnerability to me?
CVE-2026-50230 is a reflected cross-site scripting (XSS) vulnerability in Lyrion Music Server version 9.2.0 or earlier.
The vulnerability exists in the server.log endpoint, where attackers can inject arbitrary HTML and JavaScript code through the search parameter without authentication.
Attackers can craft malicious URLs containing JavaScript payloads in the search parameter to execute code in users' browsers within the context of the affected application.
How can this vulnerability impact me? :
This vulnerability allows attackers to execute arbitrary JavaScript code in the browsers of users who visit maliciously crafted URLs.
Such code execution can lead to theft of user data, session hijacking, or other malicious actions performed within the context of the vulnerable application.
Since the attack requires user interaction (clicking a malicious link), it can be used in phishing or social engineering attacks.
How can this vulnerability be detected on my network or system? Can you suggest some commands?
This vulnerability can be detected by monitoring HTTP requests to the server.log endpoint for suspicious or malicious payloads in the search parameter. Specifically, look for URLs containing JavaScript code or unusual HTML tags within the search parameter.
You can use network traffic inspection tools or web server logs to identify such requests.
- Use curl or wget to test the endpoint with a crafted URL containing a harmless JavaScript payload, for example: curl "http://<target-server>/server.log?search=<script>alert(1)</script>"
- Use grep on web server logs to find requests to server.log with suspicious search parameters: grep "server.log" /var/log/apache2/access.log | grep "search="
- Use intrusion detection systems (IDS) or web application firewalls (WAF) to detect reflected XSS patterns in HTTP requests targeting the server.log endpoint.
What immediate steps should I take to mitigate this vulnerability?
Immediate mitigation steps include applying input validation and output encoding on the search parameter in the server.log endpoint to prevent injection of arbitrary HTML and JavaScript.
If a patch or update is available from the vendor, upgrade to a fixed version of Lyrion Music Server.
As a temporary measure, consider implementing a web application firewall (WAF) rule to block or sanitize requests containing suspicious scripts in the search parameter.
Educate users to avoid clicking on suspicious URLs that may contain malicious payloads targeting this vulnerability.