CVE-2019-6512: n/a
Source CVE Database V5
Not known to be exploited.
Data as of 26 Oct 2026, 06:26 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 65% 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 2026-10-26.
What to do
Affected software
| Product | Affected | Fixed in |
|---|---|---|
Mavenorg.wso2.carbon/wso2-api-managerpkg:maven/org.wso2.carbon/wso2-api-managerOther 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
European organizations should prioritize the following mitigation steps: 1) Upgrade WSO2 API Manager to a version where this vulnerability is patched or confirmed mitigated by the vendor. If an official patch is unavailable, consider applying vendor-recommended configuration changes to disable or restrict the file:// wrapper usage. 2) Implement strict input validation and sanitization on all URL parameters processed by the API Manager to prevent SSRF payloads. 3) Employ network-level controls such as egress filtering and internal firewall rules to restrict the API Manager's ability to initiate outbound requests to internal resources, limiting the attack surface for SSRF. 4) Conduct internal network segmentation to isolate critical systems and reduce the impact of potential SSRF exploitation. 5) Monitor logs and network traffic for unusual outbound requests originating from the API Manager, which may indicate attempted exploitation. 6) Review and harden file system permissions on the server hosting the API Manager to minimize the risk of sensitive file exposure through enumeration. 7) Educate security teams about SSRF risks and ensure incident response plans include procedures for detecting and responding to such attacks.
Description
An issue was discovered in WSO2 API Manager 2.6.0. It is possible to force the application to perform requests to the internal workstation (SSRF port-scanning), other adjacent workstations (SSRF network scanning), or to enumerate files because of the existence of the file:// wrapper.