CVE-2018-20736 json
An issue was discovered in WSO2 API Manager 2.1.0 and 2.6.0.
published 7y ago modified 4mo ago also EUVD-2018-13281
- cvss
- 5.4
- version 3.0, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 1.0%
- EPSS 1.0% chance of exploitation in 30 days, percentile 62%
- public exploits
- 0
- none known
Summary
An issue was discovered in WSO2 API Manager 2.1.0 and 2.6.0. A DOM-based XSS exists in the store part of the product.
Patch / fix
Is CVE-2018-20736 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
0.98% chance of exploitation in the next 30 days, higher than 62% 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:R/S:C/C:L/I:L/A:N |
| NVD | 2.0 | 3.5 | AV:N/AC:M/Au:S/C:N/I:P/A:N |
Classification
- Weakness
-
- CWE-79 Improper Neutralization of Input During Web Page Generation
References
-
github.com
/wso2/carbon-apimgt/pull/5844/files
patch, third-party-advisory
-
wso2.com
/security-patch-releases/api-manager
patch, vendor-advisory
-
excellium-services.com
/cert-xlm-advisory/cve-2018-20736/
patch, third-party-advisory
Sources
- CVE List CVE-2018-20736
- NVD CVE-2018-20736
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.