CVE-2019-6513 json
An issue was discovered in WSO2 API Manager 2.6.0.
published 7y ago modified 4mo ago also EUVD-2019-16072
- cvss
- 5.4
- version 3.0, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 1.3%
- EPSS 1.3% chance of exploitation in 30 days, percentile 71%
- public exploits
- 0
- none known
Summary
An issue was discovered in WSO2 API Manager 2.6.0. It is possible for a logged-in user to upload, as API documentation, any type of file by changing the extension to an allowed one.
Is CVE-2019-6513 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.34% chance of exploitation in the next 30 days, higher than 71% of all scored CVEs (FIRST EPSS, 2026-11-09).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| NVD | 3.0 | 5.4 | CVSS:3.0/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:L/A:L |
| NVD | 2.0 | 5.5 | AV:N/AC:L/Au:S/C:N/I:P/A:P |
Classification
- Weakness
-
- CWE-434 Unrestricted Upload of File with Dangerous Type
References
-
excellium-services.com
/cert-xlm-advisory
third-party-advisory
-
excellium-services.com
/cert-xlm-advisory/cve-2019-6513/
third-party-advisory
- cds.thalesgroup.com /en/tcs-cert/CVE-2019-6513
Sources
- CVE List CVE-2019-6513
- NVD CVE-2019-6513
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.