CVE-2020-2194 — echarts-api
MEDIUMCVE-2020-2194 is a medium-severity (CVSS 5.4) Cross-site Scripting (XSS) vulnerability in io.jenkins.plugins:echarts-api. A fix is available for io.jenkins.plugins:echarts-api — see the affected versions and patch details below.
Stored XSS vulnerability in Jenkins ECharts API Plugin
EPSS Exploitation Probability
Probability of exploitation in the next 30 days, from FIRST.org EPSS.
How urgent is this, really
Where this sits among everything scored
Real-World Exposure
io.jenkins.plugins:echarts-apiReal-time download stats are indexed for npm and PyPI packages. This vulnerability affects Maven packages — download data is not available via public APIs for these ecosystems.
Description
ECharts API Plugin 4.7.0-3 and earlier does not escape the display name of the builds in the trend chart.
This results in a stored cross-site scripting (XSS) vulnerability that can be exploited by users with Run/Update permission.
ECharts API Plugin 4.7.0-4 escapes the display name.
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| ☕Maven | io.jenkins.plugins:echarts-api | all versions | 4.7.0-4io.jenkins.plugins:echarts-api:4.7.0-4 |
Affected Products
echarts apijenkinsDetection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for io.jenkins.plugins:echarts-api, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update io.jenkins.plugins:echarts-api to 4.7.0-4 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2020-2194 is resolved across your whole dependency graph.
Workarounds
Escape or sanitise the affected output on the server side rather than relying on client-side filtering, and add a Content-Security-Policy that blocks inline script execution so injected markup cannot run even if it reaches the page.
Frequently Asked Questions
Is CVE-2020-2194 in your dependencies?
Find it across Maven, including transitive dependencies.