Persistent XSS in Zuz Music Contact Form Administration Panel

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.

Casky was already ahead

This CVE exploits attack patterns that Casky's 301matched skills already investigate — long before this vulnerability was disclosed. Claude's reasoning model maps these techniques to MITRE ATT&CK, so practitioners who ran these skills have already seen the threat behaviour in their findings.

Analysis

Zuz Music 2.1 contains a persistent cross-site scripting (XSS) vulnerability in its contact form handler that allows unauthenticated attackers to inject malicious JavaScript code. The vulnerability exists in the `/gmusic/zuzconsole/___contact` endpoint where user-supplied input from the name, subject, and message parameters is stored without proper sanitization or encoding. When administrators later retrieve and view these contact messages in the inbox interface, the injected script executes in their browser context with administrative privileges. This affects any organization running the vulnerable Zuz Music version, particularly those relying on it for web-based music management where contact forms are publicly accessible. The CVSS 7.2 score reflects the high severity due to the ability to execute arbitrary code in an authenticated admin context without user interaction beyond normal system administration.

Casky's 301 matching skills detect this attack through analysis of MITRE ATT&CK techniques TA0001 (Reconnaissance) and TA0043 (Reconnaissance activities). Practitioners using Casky would observe detection patterns focused on CWE-79 manifestations: unsanitized input flowing from public-facing form handlers into administrative interfaces, script injection payloads in HTTP POST parameters, and execution context analysis showing code running with elevated privileges. Claude's extended reasoning capabilities would correlate the attack chain—mapping unauthenticated form submission → stored payload → admin interface rendering—and flag the persistence mechanism as the critical risk factor. Security teams would see findings highlighting the lack of input validation, absence of Content Security Policy headers, and missing output encoding in the admin console, along with recommendations for input sanitization, stored XSS prevention patterns, and administrative interface hardening aligned with OWASP Top 10 and secure development practices.

Live Threat IntelligenceComing soon

Casky Risk Score

—

EPSS Probability

—

Shodan Exposure

—

GreyNoise Signal

—

Composite risk scoring from EPSS, CISA KEV, Shodan, and GreyNoise — 21 security APIs correlated into a single Casky Risk Score. Coming in Casky Pro. Join early access →

301 Casky skills cover this attack pattern

These skills use Claude AI's reasoning model to surface findings in the same attack categories as CVE-2019-25731.

analyzing-apt-group-with-mitre-navigator

threat intelligence · low

Run

analyzing-campaign-attribution-evidence

threat intelligence · low

Run

analyzing-certificate-transparency-for-phishing

threat intelligence · low

Run

MITRE ATT&CK Techniques

TA0001 TA0043

Investigate the attack patterns behind CVE-2019-25731

Casky has 301 skills that investigate the attack patterns behind CVE-2019-25731. Run one and get CVSS-scored findings in 3 minutes.

Run the skill that detects this →

X Instagram LinkedIn