Pipeline\Application · Jenkins
CVE-2023-25762
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 Pipeline: Build Step Plugin 2.18 and earlier does not escape job names in a JavaScript expression used in the Pipeline Snippet Generator, resulting in a stored cross-site scripting (XSS) vulnerability exploitable by attackers able to control job names.
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 Pipeline: Build Step Plugin versions 2.18 and earlier fails to properly escape job names before inserting them into a JavaScript expression within the Pipeline Snippet Generator. This allows stored XSS via job names that contain malicious JavaScript payload, which executes when users interact with the snippet generator.
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
Pipeline\Application
<= 2.18CVSS 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 Pipeline: Build Step Plugin versionNavigate to Jenkins > Manage Jenkins > Manage Plugins > Installed tab, locate 'Pipeline: Build Step' in the list and note the version columnAffected if The installed version is 2.18 or earlier
-
Verify Plugin is in useCheck if any pipelines or jobs use the 'build' step from Pipeline: Build Step Plugin, or if users have access to the Pipeline Snippet Generator at /pipeline-snippet-generator/Affected if The plugin is installed and users can access the snippet generator functionality
-
Inspect job names for potential XSS payloadsList all job names in Jenkins (via API or UI) and examine them for unusual character sequences such as <script>, javascript:, onerror=, or other HTML/JavaScript patternsAffected if Any job name contains executable JavaScript or HTML that could be interpreted in a JavaScript context
You are affected if Pipeline: Build Step Plugin version 2.18 or earlier is installed AND the Pipeline Snippet Generator is accessible, with job names present that contain unsanitized JavaScript or HTML 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.
dbcve · scopedUpgrade the Jenkins Pipeline: Build Step Plugin to version 2.19 or later, which includes proper escaping of job names in JavaScript contexts. If upgrading is not immediately possible, restrict permissions around job creation to trusted users only.
Pipeline: Build Step Plugin version 2.18.1 or later
- Navigate to Jenkins dashboard
- Go to Manage Jenkins > Manage Plugins
- Click on the 'Installed' tab
- Locate 'Pipeline: Build Step Plugin' in the list
- Check if the installed version is 2.18 or earlier
- If vulnerable, click 'Check now' for updates or download version 2.18.1 or later from the Jenkins plugin repository
- Restart Jenkins after upgrading the plugin
Generated from the published advisory — verify against the referenced sources before acting.
Fix this in Pipeline\
Scoped from the published advisory
- Consultation2.0 h
- Implementation4.0 h
- Testing4.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,328.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2023-25762 — 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-2023-25762 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