CVE-2019-6513

MEDIUMNVD 5.45.4—

5.4

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.

CVSS v3: 5.4
EG Score: 5.4(medium)
EPSS: 52.8%
KEV: Not listed

Published

May 21, 2019

Last Modified

May 30, 2025

References (5)

cve@mitrehttps://cds.thalesgroup.com/en/tcs-cert/CVE-2019-6513
cve@mitrehttps://www.excellium-services.com/cert-xlm-advisory
cve@mitrehttps://www.excellium-services.com/cert-xlm-advisory/cve-2019-6513/
af854a3a-2127-422b-91ae-364da2661108https://www.excellium-services.com/cert-xlm-advisory
af854a3a-2127-422b-91ae-364da2661108https://www.excellium-services.com/cert-xlm-advisory/cve-2019-6513/

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

CWE-434Unrestricted Upload of File with Dangerous Type

Data Freshness Timeline

(refreshed 11× in last 7d / 20× in last 30d)

Every time one of our enrichment pipelines (NVD, MITRE cvelistV5, EPSS, CISA KEV, GHSA, OSV, vendor advisories) ran against this CVE. Most recent first.

2026-06-02 20:11 UTCepss_batch
2026-06-02 20:11 UTCepss_batch
2026-06-01 13:50 UTCepss_batch
2026-06-01 13:50 UTCepss_batch
2026-05-31 22:29 UTCepss_batch
2026-05-31 22:29 UTCepss_batch
2026-05-31 00:14 UTCepss_batch
2026-05-31 00:14 UTCepss_batch
2026-05-29 13:42 UTCepss_batch
2026-05-28 13:43 UTCepss_batch
2026-05-28 13:43 UTCepss_batch
2026-05-27 19:23 UTCEG score recompute
2026-05-27 19:23 UTCGHSA enrichment
2026-05-27 13:39 UTCepss_batch
2026-05-27 13:38 UTCepss_batch
2026-05-26 13:42 UTCepss_batch
2026-05-26 07:17 UTCepss_batch
2026-05-26 07:17 UTCepss_batch
2026-05-26 07:17 UTCepss_batch
2026-05-24 16:47 UTCepss_batch

Frequently asked(5)

What is CVE-2019-6513?

CVE-2019-6513 is a medium vulnerability published on May 21, 2019. 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.

When was CVE-2019-6513 disclosed?

CVE-2019-6513 was first published in the National Vulnerability Database on May 21, 2019, with the most recent update on May 30, 2025. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.

Is CVE-2019-6513 actively exploited?

CVE-2019-6513 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 52.8% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.

What is the CVSS score of CVE-2019-6513?

CVE-2019-6513 has a CVSS v3 base score of 5.4 (NVD).

How do I remediate CVE-2019-6513?

Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2019-6513, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2019-6513

Explore →

Is Your Infrastructure Affected by CVE-2019-6513?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Start Free Scan →Browse All CVEs

CVE-2019-6513

📅 Published

🔄 Last Modified

🔗 References (5)

Weakness Classification(1)

Data Freshness Timeline

❓ Frequently asked(5)

Dependency Blast Radius

Is Your Infrastructure Affected by CVE-2019-6513?

🔗 Related CVEs(same CWE)

Same CWE

Published

Last Modified

References (5)

Frequently asked(5)

Related CVEs(same CWE)