Build With ParametersApplication · Jenkins
CVE-2021-21628
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 Build With Parameters Plugin 1.5 and earlier does not escape parameter names and descriptions, 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 Build With Parameters Plugin versions 1.5 and earlier fails to properly escape output for parameter names and descriptions. An authenticated attacker with Job/Configure permission can inject malicious JavaScript into these fields, which executes when other users view the parameter configuration page.
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
Build With ParametersApplication
<= 1.5CVSS 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.
-
Check Build With Parameters Plugin versionNavigate to Jenkins > Manage Jenkins > Manage Plugins > Installed tab, or use the CLI: java -jar jenkins-cli.jar list-plugins Build With ParametersAffected if Plugin is installed and version is 1.5 or earlier (or version cannot be determined)
-
Verify plugin is actually used in jobsSearch job configs for <buildWrappers> containing build_with_parameters or parameter names with special characters. Inspect config.xml files in JENKINS_HOME/jobs/*/config.xml for <hudson.model.ParametersDefinitionProperty> sectionsAffected if Jobs exist that use the Build With Parameters plugin with custom parameter definitions
-
Inspect parameter names and descriptions for injected codeReview all parameter names and descriptions in job configurations. Look for unescaped HTML, JavaScript tags, or event handlers like <script>, onclick, onerror, or javascript: URIsAffected if Any parameter name or description contains raw HTML or JavaScript code that would execute in a browser
-
Check recent job configuration changesReview Jenkins audit logs or job configuration history for recent changes to parameter definitions by users with Job/Configure permissionAffected if Suspicious modifications to parameter names/descriptions are present
-
Test XSS vulnerability directlyCreate a test job with Build With Parameters, add a parameter with name containing <script>alert(1)</script>, save, and view the parameter configuration pageAffected if The script executes or renders unescaped when viewing the configuration page
A user is affected if the Build With Parameters Plugin version is 1.5 or earlier AND the plugin is in use with configurable parameters that could contain injected script content.
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 Build With Parameters Plugin to version 1.6 or later which includes proper escaping. Review job configurations for any existing malicious parameter entries before upgrading.
Fix this in Build With Parameters
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-21628 — 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-21628 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