Extra ColumnsApplication · Jenkins
CVE-2021-21630
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 Extra Columns Plugin 1.22 and earlier does not escape parameter values in the build parameters column, resulting in a stored cross-site scripting (XSS) vulnerability exploitable by attackers with Job/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 Extra Columns Plugin versions 1.22 and earlier fails to properly escape parameter values displayed in the build parameters column, allowing stored XSS attacks. Attackers with Job/Configure permission can inject malicious scripts via parameter values that execute when viewed by other users.
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
Extra ColumnsApplication
<= 1.22CVSS 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.
-
Verify Extra Columns plugin is installedNavigate to Manage Jenkins > Manage Plugins > Installed tab and search for 'Extra Columns', or inspect the plugin directory (typically $JENKINS_HOME/plugins/extra-columns/) for the .jpi or .hpi fileAffected if The plugin is present on the Jenkins instance
-
Determine installed plugin versionIn the Installed Plugins tab, check the version column for Extra Columns plugin, or examine the plugin manifest file (META-INF/MANIFEST.MF) inside the plugin archiveAffected if Version is 1.22 or earlier (e.g., 1.22, 1.21, 1.20, etc.)
-
Check if build parameters column is configuredNavigate to Manage Jenkins > Configure System > Extra Columns section, or go to a specific view's configuration, and verify if the 'Build Parameters' column is added and visibleAffected if The Build Parameters column is enabled and displayed in any view
-
Review Job/Configure permission assignmentsNavigate to Manage Jenkins > Manage and Assign Permissions, and review which users or groups have the Job/Configure permission (typically found in the 'Overall' or 'Job' permission categories)Affected if Users or groups outside the trusted admin set possess Job/Configure permission, allowing them to configure job parameters
You are affected if the Extra Columns plugin version is 1.22 or earlier, the Build Parameters column is in use, and untrusted users have Job/Configure permission to inject malicious parameter values.
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 Extra Columns Plugin to version 1.23 or later which contains proper output encoding. Until patched, restrict Job/Configure permission to only trusted users.
Fix this in Extra Columns
Scoped from the published advisory
- Consultation1.0 h
- Implementation2.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,664.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2021-21630 — 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-21630 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