CVE-2019-25731
Persistent XSS in Zuz Music Contact Form
Publication date: 2026-06-04
Last updated on: 2026-06-04
Assigner: VulnCheck
Description
Description
CVSS Scores
EPSS Scores
| Probability: | |
| Percentile: |
Meta Information
Affected Vendors & Products
| Vendor | Product | Version / Range |
|---|---|---|
| kamranwajdani | zuz_music | 2.1 |
| kamranwajdani | zuz_music | to 2.1 (inc) |
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-2019-25731 is a persistent cross-site scripting (XSS) vulnerability in Zuz Music version 2.1. It allows unauthenticated attackers to inject malicious JavaScript code by submitting crafted data through the name, subject, and message fields in POST requests to the /gmusic/zuzconsole/___contact endpoint.
The injected script executes when administrators view the messages in the inbox interface, potentially compromising the administrator's browser session or enabling other malicious actions.
How can this vulnerability impact me? :
This vulnerability can impact you by allowing attackers to execute malicious JavaScript in the context of an administrator's browser when they view the inbox messages.
- Attackers can hijack administrator sessions.
- They can perform unauthorized actions on behalf of the administrator.
- It may lead to data theft or further exploitation of the system.
How can this vulnerability be detected on my network or system? Can you suggest some commands?
This vulnerability can be detected by testing the /gmusic/zuzconsole/___contact endpoint for persistent cross-site scripting (XSS) by submitting crafted POST requests with malicious JavaScript code in the name, subject, and message parameters.
A practical approach is to send POST requests with script tags or JavaScript payloads in these fields and then verify if the injected script executes when viewing the messages in the administrator inbox interface.
Example command using curl to test injection:
- curl -X POST https://[target]/gmusic/zuzconsole/___contact -d "name=<script>alert('XSS')</script>&subject=test&message=test"
After sending such a request, check the admin inbox interface to see if the alert or injected script executes, indicating the presence of the vulnerability.
How does this vulnerability affect compliance with common standards and regulations (like GDPR, HIPAA)?:
The provided information does not specify how the CVE-2019-25731 vulnerability affects compliance with common standards and regulations such as GDPR or HIPAA.
What immediate steps should I take to mitigate this vulnerability?
Immediate mitigation steps include sanitizing and validating all input fields (name, subject, message) on the /gmusic/zuzconsole/___contact endpoint to prevent injection of malicious scripts.
Administrators should avoid viewing untrusted messages in the inbox interface until the vulnerability is patched.
Applying updates or patches provided by the vendor or upgrading to a version of Zuz Music that addresses this vulnerability is strongly recommended.
Additionally, implementing Content Security Policy (CSP) headers can help mitigate the impact of injected scripts.