CVE-2019-6515: WSO2 API Manager
Source CVE Database V5
Not known to be exploited.
Data as of 26 Oct 2026, 09:15 UTC
Rated Medium by the CNA (mitre) · No CVSS score from NVD or the CNA
- EPSS
- 1.5% chance of exploitation in 30 days – higher than 74% 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 |
|---|---|---|
| n/a n/a | Affected
| Fixed in– |
AI-suggested
European organizations using WSO2 API Manager 2.6.0 should immediately audit their API documentation upload and access controls. Specific mitigation steps include: 1) Restrict access to uploaded API documentation files by enforcing authentication and authorization checks at the web server or application level. 2) Review and update API Manager configurations to ensure that documentation endpoints are not publicly accessible without proper credentials. 3) Implement network-level controls such as firewalls or reverse proxies to limit access to documentation resources. 4) Monitor access logs for unusual or unauthorized access attempts to documentation files. 5) Engage with WSO2 support or community channels to obtain patches or updates addressing this vulnerability. 6) If patches are unavailable, consider upgrading to a later version of WSO2 API Manager where this issue is resolved. 7) Educate developers and administrators on secure API documentation handling practices to prevent inadvertent exposure.
Description
An issue was discovered in WSO2 API Manager 2.6.0. Uploaded documents for API documentation are available to an unauthenticated user.