CVE-2019-6516 json
An issue was discovered in WSO2 Dashboard Server 2.0.0.
published 7y ago modified 4mo ago also EUVD-2019-16075
- cvss
- 5.8
- version 3.0, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 1.6%
- EPSS 1.6% chance of exploitation in 30 days, percentile 75%
- public exploits
- 0
- none known
Summary
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.
Is CVE-2019-6516 in your stack? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.
Check with FencerExploit prediction
1.56% chance of exploitation in the next 30 days, higher than 75% of all scored CVEs (FIRST EPSS, 2026-11-09).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| NVD | 3.0 | 5.8 | CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:C/C:L/I:N/A:N |
| NVD | 2.0 | 5.0 | AV:N/AC:L/Au:N/C:P/I:N/A:N |
Classification
- Weakness
-
- CWE-918 Server-Side Request Forgery
References
-
wso2.com
/security-patch-releases/dashboard-server
vendor-advisory
-
excellium-services.com
/cert-xlm-advisory
third-party-advisory
- cds.thalesgroup.com /en/tcs-cert/CVE-2019-6516
Sources
- CVE List CVE-2019-6516
- NVD CVE-2019-6516
Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.