CVE-2019-25731: Zuz Music 2.1 Persistent Cross-site Scripting via zuzconsole Contact
Zuz Music 2.1 contains a persistent cross-site scripting vulnerability that allows unauthenticated attackers to inject malicious JavaScript by submitting crafted contact form data. Attackers can inject script code through the name, subject, and message parameters in POST requests to /gmusic/zuzconsole/___contact, which executes when administrators view messages in the inbox interface.
Security readout for executives and security teams
Plain-English summary
Zuz Music 2.1 lets an unauthenticated visitor store JavaScript through the contact form. The script can run later when an administrator opens the inbox. This is not a server takeover by itself, but it can expose admin session data or drive unauthorized actions in the admin browser.
Executive priority
Prioritize remediation for internet-facing Zuz Music 2.1 sites, especially where administrators regularly use the web inbox. The business risk is admin-browser compromise, not direct database compromise from the CVE description alone.
Technical view
Persistent XSS affects POST handling for /gmusic/zuzconsole/___contact. The reported injectable fields are name, subject, and message. Execution occurs in the administrator inbox view, requiring admin interaction. CVSS 3.1 is 6.1 with network attack vector, low complexity, no privileges, and changed scope.
Likely exposure
Exposure is limited to deployments running Zuz Music 2.1 with the contact endpoint reachable and administrators reviewing submitted messages in the web inbox.
Exploitation context
The bundle cites a public ExploitDB entry, so proof-of-concept information exists. It does not show CISA KEV listing or active exploitation evidence. Treat this as plausible opportunistic risk for internet-facing sites, not confirmed in-the-wild exploitation.
Researcher notes
Evidence is specific to Zuz Music 2.1 and the contact workflow. The CVE record was published June 4, 2026, despite the 2019 identifier. No source in the bundle names a fixed version or confirms active exploitation.
Mitigation direction
Check vendor or marketplace guidance for an updated Zuz Music release or advisory.
Upgrade, patch, or retire Zuz Music 2.1 where feasible.
Restrict administrative access and require strong session protections for admin users.
If maintaining code, encode inbox output and validate stored contact fields.
Review and remove suspicious stored contact messages before admin access.
Validation and detection
Inventory public sites for Zuz Music 2.1 or matching Zuz Music components.
Confirm whether /gmusic/zuzconsole/___contact is internet reachable.
Review the admin inbox rendering path for untrusted contact data.
Inspect stored contact submissions for script-like content or unusual HTML.
Verify fixes by ensuring submitted text renders inert in the inbox.
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Potential ATT&CK relevance
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
cwe · medium confidence lookup
CWE-79: User-session and phishing behavior lookup
Client-side and session-facing weaknesses should be reviewed alongside initial-access and user-execution behaviors. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
CWE-79 · source CWE mapping
Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting')
Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting') represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.