Template WorkflowsApplication · Jenkins
CVE-2023-35146
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 Template Workflows Plugin 41.v32d86a_313b_4a and earlier does not escape names of jobs used as buildings blocks for Template Workflow Job, resulting in a stored cross-site scripting (XSS) vulnerability exploitable by attackers able to create jobs.
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 Template Workflows Plugin versions 41.v32d86a_313b_4a and earlier fails to properly escape job names used as building blocks when creating Template Workflow Jobs. This allows attackers with job creation privileges to inject malicious JavaScript code into job names, which executes in the browsers of other users who view the template job configuration or related pages.
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
Template WorkflowsApplication
<= 41.v32d86a_313b_4aCVSS 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 Template Workflows Plugin is installedGo to Jenkins > Manage Jenkins > Manage Plugins > Installed tab and search for 'Template Workflows' or check the plugin directory $JENKINS_HOME/plugins for the template-workflows plugin folderAffected if The plugin is present in the plugins directory or listed in Installed plugins
-
Determine the installed plugin versionIn Manage Jenkins > Manage Plugins > Installed tab, find Template Workflows and note the version number displayed in the version columnAffected if Version is 41.v32d86a_313b_4a or earlier (the version string contains 41.v32d86a_313b_4a or a lower version number)
-
Check for job creation permissionsGo to Manage Jenkins > Manage Users and review who has the Overall/Administer or Job/Create permissions, or inspect $JENKINS_HOME/users/ directory for user directoriesAffected if Multiple users exist with job creation privileges, especially untrusted or anonymous users have this access
-
Inspect existing Template Workflow Jobs for suspicious job namesBrowse to the Template Workflow jobs in Jenkins and examine job names. Look for jobs containing characters like <script>, javascript:, onerror=, or unusual encoded characters in the job name fieldAffected if Any Template Workflow Job exists with a job name containing XSS payloads such as <script> tags, javascript: URIs, or event handler attributes like onload/onerror
You are affected if the Template Workflows Plugin version is 41.v32d86a_313b_4a or earlier AND users with job creation permissions exist AND any Template Workflow Job has a suspicious name containing script tags or JavaScript event handlers.
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 the Jenkins Template Workflows Plugin to version 41.v32d86a_313b_4a or later. Until patched, restrict job creation permissions to trusted users only.
Fix this in Template Workflows
Scoped from the published advisory
- Consultation2.0 h
- Implementation1.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 $2,464.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2023-35146 — 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-35146 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