Chosen Views TabbarApplication · Jenkins

CVE-2020-2269

MEDIUM · 5.4 CVSS v3.1 Published 2020-09-16
Fix available
A fix is available. Upgrade to after 1.2 or later.
See remediation →
58/100
Remediation priority · Elevated
Remotely reachable

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 · unedited
Jenkins chosen-views-tabbar Plugin 1.2 and earlier does not escape view names in the dropdown to select views, resulting in a stored cross-site scripting (XSS) vulnerability exploitable by attackers with the ability to configure views.

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 confidence

The Jenkins chosen-views-tabbar Plugin versions 1.2 and earlier fails to properly escape view names before rendering them in the dropdown menu used to select views. This allows an attacker with permissions to configure views to inject malicious JavaScript code that executes when other users view or interact with the view dropdown, resulting in a stored cross-site scripting (XSS) vulnerability.

MitigationUpdate the Jenkins chosen-views-tabbar Plugin to version 1.3 or later, which includes proper output encoding of view names. Until patched, restrict view configuration permissions to trusted administrators only.

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
Chosen Views TabbarApplication
Affected:<= 1.2

CVSS 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 checks

Work through these to decide whether this CVE applies to you.

  1. Verify chosen-views-tabbar plugin is installed
    Navigate to Jenkins > Manage Jenkins > Manage Plugins > Installed, or check the file system for the plugin manifest at $JENKINS_HOME/plugins/chosen-views-tabbar/META-INF/MANIFEST.MF
    Affected if The plugin is present in the Jenkins instance
  2. Determine the installed plugin version
    Read the Plugin-Version from the manifest file at $JENKINS_HOME/plugins/chosen-views-tabbar/META-INF/MANIFEST.MF, or view the version in the Jenkins plugin manager UI
    Affected if The version is 1.2 or earlier (the affected range is <= 1.2)
  3. Identify users with view configuration permissions
    Navigate to Jenkins > Manage Jenkins > Manage and Assign Permissions. Check which users or groups have the 'Overall/Administer' permission versus lower-privileged permissions. Review view-level permissions in the security matrix
    Affected if Non-administrator users have permissions to configure or create views, as the attacker needs this access to inject malicious view names
  4. Inspect existing views for unusual names
    Navigate to the Jenkins home page, click the views dropdown, and review all view names for characters that could be used in XSS payloads (such as <script>, javascript:, onerror=, or unusual encoding)
    Affected if Any view names contain potentially malicious JavaScript content or unusual characters typical of XSS injection attempts

The environment is affected if the chosen-views-tabbar plugin version 1.2 or earlier is installed AND non-administrator users have view configuration permissions, creating conditions for stored XSS injection.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 data
Upgrade available Upgrade to a release after 1.2
Interim mitigation

Update the Jenkins chosen-views-tabbar Plugin to version 1.3 or later, which includes proper output encoding of view names. Until patched, restrict view configuration permissions to trusted administrators only.

Fix this in Chosen Views Tabbar Scoped from the published advisory
  • Consultation2.0 h
  • Implementation1.0 h
  • Testing3.0 h
  • Review / QA2.0 h
8.0 hours of engineering $1,390
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,224.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2020-2269 — 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 sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2020-2269 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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