VulnerabilityPublished 14 May 2019Updated 30 May 2025

CVE-2019-6516: WSO2 Dashboard Server

Source CVE Database V5

Not known to be exploited.

Data as of 26 Oct 2026, 17:16 UTC

Severity

High

Rated High by the CNA (mitre) · No CVSS score from NVD or the CNA

EPSS: 1.5% chance of exploitation in 30 days – higher than 75% 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.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponised: Public exploit code exists in Metasploit or Exploit-DB, or CISA SSVC or the CVSS exploit maturity reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

What to do

Affected software

Product	Affected	Fixed in
n/a n/a	Affected =2.0.0	Fixed in–

AI-suggested

To mitigate CVE-2019-6516, European organizations should first identify all deployments of WSO2 Dashboard Server 2.0.0 within their networks. In the interim, network segmentation should be enforced to limit the Dashboard Server's ability to access sensitive internal resources. Implement strict egress and ingress firewall rules to restrict the server's outbound requests to only trusted destinations. Application-level controls such as input validation and request filtering should be applied to prevent malicious request parameters that could trigger SSRF. Monitoring and logging of outbound requests from the Dashboard Server should be enhanced to detect anomalous scanning activity. If feasible, consider deploying Web Application Firewalls (WAFs) with SSRF detection capabilities. Finally, conduct regular security assessments and penetration tests focused on SSRF and internal reconnaissance vectors to validate the effectiveness of mitigations.

Description

An issue was discovered in WSO2 Dashboard Server 2.0.0. It is possible to force the application to perform requests to the internal workstation (port-scanning) and to perform requests to adjacent workstations (network-scanning), aka SSRF.

Impact

For European organizations, this SSRF vulnerability poses a significant risk to internal network confidentiality and integrity. By enabling attackers to perform internal port and network scanning, it can facilitate the discovery of critical infrastructure components, internal services, and potentially vulnerable endpoints that are otherwise shielded by perimeter defenses. This reconnaissance capability can be leveraged to plan further attacks such as privilege escalation, lateral movement, or targeted exploitation of internal systems. Organizations handling sensitive data, including financial institutions, healthcare providers, and government agencies, could face increased risk of data breaches or service disruptions. Additionally, the exposure of internal network details could violate data protection regulations such as GDPR if it leads to unauthorized access or data leakage. The absence of authentication requirements for exploitation increases the threat level, especially for publicly accessible instances of the WSO2 Dashboard Server. The impact on availability is indirect but possible if attackers leverage discovered vulnerabilities to launch denial-of-service attacks or disrupt monitoring capabilities.

References

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 8 Jul 2025, 15:10 UTC

Technical details

References

Community reviews

Related threats