CVE-2019-6514: n/a
Source CVE Database V5
Not known to be exploited.
Data as of 26 Oct 2026, 08:30 UTC
Rated High by the CNA (mitre) · No CVSS score from NVD or the CNA
- EPSS
- 1.0% chance of exploitation in 30 days – higher than 62% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Exploitation evidence
Disclosed: evidence found.
CVE published 14 May 2019
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.
What to do
Affected software
| Product | Affected | Fixed in |
|---|---|---|
Mavenorg.wso2/dashboard-serverpkg:maven/org.wso2/dashboard-serverOther threats | Affected
| Fixed in– |
Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.
AI-suggested
To mitigate CVE-2019-6514, European organizations should first verify if they are running WSO2 Dashboard Server version 2.0.0 or any other potentially affected versions. Immediate steps include: 1) Implement strict input validation and output encoding on all user-supplied data fields within the dashboard application to prevent injection of malicious scripts. 2) Apply any available vendor patches or updates; if none are available, contact WSO2 support for guidance or consider upgrading to a later, patched version. 3) Employ Content Security Policy (CSP) headers to restrict the execution of unauthorized scripts in the browser context. 4) Conduct thorough code reviews and security testing focusing on XSS vulnerabilities in the dashboard application. 5) Limit user permissions to reduce the impact of a successful exploit, ensuring that only trusted users can input data that is rendered to others. 6) Monitor logs and user activity for unusual behavior indicative of exploitation attempts. 7) Educate users about the risks of XSS and encourage cautious behavior when interacting with dashboard content. These measures, combined, will reduce the likelihood and impact of exploitation.
Description
An issue was discovered in WSO2 Dashboard Server 2.0.0. It is possible to inject a JavaScript payload that will be stored in the database and then displayed and executed on the same page, aka XSS.