CVE-2021-21649 is a medium-severity (CVSS 5.4) Cross-site Scripting (XSS) vulnerability in org.jenkins-ci.plugins:dashboard-view. EPSS puts its 30-day exploitation probability at 72.7% (99th percentile). A fix is available for org.jenkins-ci.plugins:dashboard-view — see the affected versions and patch details below.
Cross-site Scripting in Jenkins Dashboard View 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
org.jenkins-ci.plugins:dashboard-view☕org.jenkins-ci.plugins:dashboard-viewReal-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
Jenkins Dashboard View Plugin prior to 2.16 and 2.12.1 does not escape URLs referenced in Image Dashboard Portlets, resulting in a stored cross-site scripting (XSS) vulnerability exploitable by attackers with View/Configure permission.
As part of this fix, the property for image URLs was changed from url to imageUrl. Existing Configuration as Code configurations are still supported, but exports will emit the new property.
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| ☕Maven | org.jenkins-ci.plugins:dashboard-view | ≥ 2.13&&< 2.16 | 2.16org.jenkins-ci.plugins:dashboard-view:2.16 |
| ☕Maven | org.jenkins-ci.plugins:dashboard-view | all versions | 2.12.1org.jenkins-ci.plugins:dashboard-view:2.12.1 |
Affected Products
dashboard viewjenkinsDetection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for org.jenkins-ci.plugins:dashboard-view, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update org.jenkins-ci.plugins:dashboard-view to 2.16 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2021-21649 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-2021-21649 in your dependencies?
Find it across Maven, including transitive dependencies.