Dashboard ViewApplication · Jenkins
CVE-2021-21649
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedJenkins Dashboard View Plugin 2.15 and earlier 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.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · high confidenceThe Jenkins Dashboard View Plugin versions 2.15 and earlier fails to properly escape URLs in Image Dashboard Portlets. This allows authenticated attackers with View/Configure permission to inject malicious scripts via crafted URLs, resulting in stored XSS that executes when other users view the affected dashboard.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data
Dashboard ViewApplication
<= 2.15CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- Low
- User interaction
- Required
- Scope
- Changed
- Confidentiality
- Low
- Integrity
- Low
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:C/C:L/I:L/A:N
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Identify if Jenkins Dashboard View Plugin is installedNavigate to Manage Jenkins > Manage Plugins > Installed tab and search for 'Dashboard View', or run: jenkins-cli.jar who-am-i (or check $JENKINS_HOME/plugins for dashboard-view folder)Affected if The Dashboard View plugin appears in the installed plugins list
-
Determine the installed version of Dashboard View PluginIn Jenkins UI, go to Manage Jenkins > Manage Plugins > Installed > Dashboard View, note the version shown. Alternatively, inspect $JENKINS_HOME/plugins/dashboard-view/META-INF/MANIFEST.MF for the Plugin-VersionAffected if The version is 2.15 or lower (e.g., 2.15, 2.14, 2.13, etc.)
-
Check for existing Image Dashboard Portlets in any viewsOpen each Jenkins view configured as a Dashboard View. Look for 'Image Dashboard' portlet type in the view configuration. Check view config XML files in $JENKINS_HOME/jobs/*/config.xml or via REST API: GET /api/json?tree=views[name,url,property[config]]Affected if One or more views contain an Image Dashboard portlet with a configured URL
-
Verify if users with limited permissions can configure viewsReview Matrix Authorization Strategy or Project-based Matrix Authorization settings. Check which users or groups have the Overall/Read and Job/Configure or View/Configure permissionsAffected if Users other than administrators have View/Configure or Job/Configure permission enabled
User is affected if Dashboard View Plugin version 2.15 or earlier is installed AND Image Dashboard portlets are in use AND untrusted users have View/Configure permission.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
From vendor dataUpdate Jenkins Dashboard View Plugin to version 2.16 or later which includes proper URL encoding. If immediate update is not possible, restrict View/Configure permissions to trusted users only.
Fix this in Dashboard View
Scoped from the published advisory
- Consultation2.0 h
- Implementation1.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,696.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2021-21649 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2021-21649 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data