An issue was discovered in WSO2 API Manager 2.6.0.

published 2019-05-14 7y ago modified 2026-06-17 4mo ago also EUVD-2019-16074

cvss: 5.3; version 3.0, NVD
cisa kev: Not listed; not in CISA's catalog
epss: 1.5%; EPSS 1.5% chance of exploitation in 30 days, percentile 75%
public exploits: 0; none known

An issue was discovered in WSO2 API Manager 2.6.0. Uploaded documents for API documentation are available to an unauthenticated user.

Patch / fix

links 1

wso2.com/security-patch-releases/api-manager advisory

Is CVE-2019-6515 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 Fencer

Exploit prediction

1.54% 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.3	CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N
NVD	2.0	5.0	AV:N/AC:L/Au:N/C:P/I:N/A:N

References

wso2.com /security-patch-releases/api-manager
patch, vendor-advisory
excellium-services.com /cert-xlm-advisory
third-party-advisory
cds.thalesgroup.com /en/tcs-cert/CVE-2019-6515

Sources

CVE List CVE-2019-6515
NVD CVE-2019-6515

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.