CVE-2019-25731

MEDIUMPre-NVD 6.17.2
EchelonGraph scoreMEDIUM confidence

Score 7.2 from GitHub Security Advisory published 2026-06-04. a secondary CVSS source baseline 6.1; sources differ by 1.1.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, secondary
Trending — 3 sources updated this weekElevated
6.1
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS: 0%CVSS: 6.1Exploit: NoneExposed: 0

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

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.

CVSS v3
6.1
EG Score
7.2(medium)
EPSS
11.3%
KEV
Not listed

Published

June 4, 2026

Last Modified

June 10, 2026

Advisory Details (2)

Auto-updated Jun 13, 2026
🔬 Proof of concept available. No patch confirmed yet.
generic

Zuz Music 2.1 Persistent Cross-site Scripting via zuzconsole Contact | Advisories | VulnCheck

https://www.vulncheck.com/advisories/zuz-music-persistent-cross-site-scripting-via-zuzconsole-contact
generic🟡 PoC Available

Zuz Music 2.1 - 'zuzconsole/___contact ' Persistent Cross-Site Scripting - PHP webapps Exploit

https://www.exploit-db.com/exploits/46420

Vendor Advisories for CVE-2019-25731(1)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 18× in last 7d / 107× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

Showing the most recent 100 of 168 total refreshes for this CVE.

  1. 2026-07-15 16:55 UTCEPSS rescore
  2. 2026-07-15 16:55 UTCEPSS rescore
  3. 2026-07-14 16:26 UTCEG score recompute
  4. 2026-07-14 16:26 UTCGHSA enrichment
  5. 2026-07-14 03:23 UTCEG score recompute
  6. 2026-07-14 03:23 UTCGHSA enrichment
  7. 2026-07-13 22:27 UTCEPSS rescore
  8. 2026-07-13 06:10 UTCEPSS rescore
  9. 2026-07-13 06:10 UTCEPSS rescore
  10. 2026-07-12 05:43 UTCEPSS rescore
  11. 2026-07-12 05:43 UTCEPSS rescore
  12. 2026-07-12 00:47 UTCEG score recompute
  13. 2026-07-12 00:47 UTCGHSA enrichment
  14. 2026-07-11 12:19 UTCEG score recompute
  15. 2026-07-11 12:19 UTCGHSA enrichment
  16. 2026-07-11 08:24 UTCEPSS rescore
  17. 2026-07-11 08:24 UTCEPSS rescore
  18. 2026-07-09 19:06 UTCEPSS rescore
  19. 2026-07-08 22:33 UTCEG score recompute
  20. 2026-07-08 22:33 UTCGHSA enrichment
  21. 2026-07-08 15:11 UTCEPSS rescore
  22. 2026-07-08 10:03 UTCEG score recompute
  23. 2026-07-08 10:03 UTCGHSA enrichment
  24. 2026-07-07 13:43 UTCEPSS rescore
  25. 2026-07-06 16:25 UTCEPSS rescore
Show 75 more
  1. 2026-07-06 16:25 UTCEPSS rescore
  2. 2026-07-06 02:20 UTCEPSS rescore
  3. 2026-07-05 02:27 UTCEPSS rescore
  4. 2026-07-04 06:28 UTCEPSS rescore
  5. 2026-07-03 19:23 UTCEG score recompute
  6. 2026-07-03 19:23 UTCGHSA enrichment
  7. 2026-07-02 21:52 UTCEG score recompute
  8. 2026-07-02 21:52 UTCGHSA enrichment
  9. 2026-07-02 09:29 UTCEG score recompute
  10. 2026-07-02 09:29 UTCGHSA enrichment
  11. 2026-07-01 21:06 UTCEG score recompute
  12. 2026-07-01 21:06 UTCGHSA enrichment
  13. 2026-07-01 15:03 UTCEPSS rescore
  14. 2026-07-01 15:03 UTCEPSS rescore
  15. 2026-07-01 08:43 UTCEG score recompute
  16. 2026-07-01 08:43 UTCGHSA enrichment
  17. 2026-06-30 23:20 UTCEPSS rescore
  18. 2026-06-30 20:19 UTCEG score recompute
  19. 2026-06-30 20:19 UTCGHSA enrichment
  20. 2026-06-29 22:28 UTCEG score recompute
  21. 2026-06-29 22:28 UTCGHSA enrichment
  22. 2026-06-29 14:03 UTCEPSS rescore
  23. 2026-06-29 10:05 UTCEG score recompute
  24. 2026-06-29 10:05 UTCGHSA enrichment
  25. 2026-06-28 17:14 UTCEG score recompute
  26. 2026-06-28 17:14 UTCGHSA enrichment
  27. 2026-06-28 14:04 UTCEPSS rescore
  28. 2026-06-28 04:54 UTCEPSS rescore
  29. 2026-06-28 04:54 UTCEPSS rescore
  30. 2026-06-28 04:41 UTCEG score recompute
  31. 2026-06-28 04:41 UTCGHSA enrichment
  32. 2026-06-27 16:11 UTCEG score recompute
  33. 2026-06-27 16:11 UTCGHSA enrichment
  34. 2026-06-27 03:45 UTCEG score recompute
  35. 2026-06-27 03:45 UTCGHSA enrichment
  36. 2026-06-27 03:06 UTCEPSS rescore
  37. 2026-06-26 14:59 UTCEG score recompute
  38. 2026-06-26 14:59 UTCGHSA enrichment
  39. 2026-06-25 22:58 UTCEG score recompute
  40. 2026-06-25 22:58 UTCGHSA enrichment
  41. 2026-06-25 13:47 UTCEPSS rescore
  42. 2026-06-25 13:47 UTCEPSS rescore
  43. 2026-06-25 10:34 UTCEG score recompute
  44. 2026-06-25 10:33 UTCGHSA enrichment
  45. 2026-06-24 22:11 UTCEG score recompute
  46. 2026-06-24 22:10 UTCGHSA enrichment
  47. 2026-06-24 14:03 UTCEPSS rescore
  48. 2026-06-24 14:03 UTCEPSS rescore
  49. 2026-06-24 09:05 UTCEG score recompute
  50. 2026-06-24 09:05 UTCGHSA enrichment
  51. 2026-06-23 21:31 UTCEPSS rescore
  52. 2026-06-23 21:30 UTCEPSS rescore
  53. 2026-06-23 18:50 UTCEG score recompute
  54. 2026-06-23 18:49 UTCGHSA enrichment
  55. 2026-06-23 02:26 UTCEG score recompute
  56. 2026-06-23 02:26 UTCGHSA enrichment
  57. 2026-06-22 14:23 UTCEPSS rescore
  58. 2026-06-21 14:54 UTCEPSS rescore
  59. 2026-06-21 14:54 UTCEPSS rescore
  60. 2026-06-21 01:57 UTCEPSS rescore
  61. 2026-06-21 01:57 UTCEPSS rescore
  62. 2026-06-20 12:12 UTCEG score recompute
  63. 2026-06-20 12:12 UTCGHSA enrichment
  64. 2026-06-19 20:06 UTCEG score recompute
  65. 2026-06-19 20:06 UTCGHSA enrichment
  66. 2026-06-19 19:23 UTCEPSS rescore
  67. 2026-06-19 19:23 UTCEPSS rescore
  68. 2026-06-19 04:27 UTCEG score recompute
  69. 2026-06-19 04:27 UTCGHSA enrichment
  70. 2026-06-18 17:50 UTCEPSS rescore
  71. 2026-06-18 15:00 UTCEG score recompute
  72. 2026-06-18 15:00 UTCGHSA enrichment
  73. 2026-06-18 01:15 UTCEG score recompute
  74. 2026-06-18 01:15 UTCGHSA enrichment
  75. 2026-06-17 17:50 UTCEPSS rescore

Frequently asked(5)

What is CVE-2019-25731?
CVE-2019-25731 is a medium vulnerability published on June 4, 2026. 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…
When was CVE-2019-25731 disclosed?
CVE-2019-25731 was first published in the National Vulnerability Database on June 4, 2026, with the most recent update on June 10, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2019-25731 actively exploited?
CVE-2019-25731 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 11.3% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
What is the CVSS score of CVE-2019-25731?
CVE-2019-25731 has a CVSS v3 base score of 6.1 (NVD). EchelonGraph synthesises NVD + CISA KEV + FIRST EPSS + GHSA into a combined EG score of 7.2.
How do I remediate CVE-2019-25731?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2019-25731, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

Explore the affected products and dependency analysis for CVE-2019-25731

Explore →

Is Your Infrastructure Affected by CVE-2019-25731?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.