CVE-2023-40346
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 Shortcut Job Plugin 0.4 and earlier does not escape the shortcut redirection URL, resulting in a stored cross-site scripting (XSS) vulnerability exploitable by attackers able to configure shortcut 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 Shortcut Job Plugin versions 0.4 and earlier fails to escape/sanitize the shortcut redirection URL before rendering it in web pages, resulting in a stored cross-site scripting (XSS) vulnerability. Attackers with permission to configure shortcut jobs can inject malicious JavaScript code into the redirection URL that will execute in the browsers of users who view the affected 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<= 0.4CVSS 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 the Shortcut Job Plugin is installedNavigate to Jenkins > Manage Jenkins > Manage Plugins > Installed tab, then search for 'Shortcut Job' in the filter to confirm the plugin is present.Affected if The plugin does not appear in the installed plugins list, meaning it is not in use.
-
Determine the installed version of the Shortcut Job PluginIn the Installed plugins tab, locate the Shortcut Job plugin and note the Version column displayed in the plugin table.Affected if The displayed version is 0.4 or lower (e.g., 0.4, 0.3, 0.2, 0.1, or any version number less than or equal to 0.4).
-
Check if shortcut jobs exist in the systemUse the Jenkins search or browse to jobs configured with the Shortcut Job type, or run: jenkins-cli.jar get-job [job-name] (if available) to inspect job configurations for shortcut job definitions.Affected if No jobs using the Shortcut Job plugin are configured in the Jenkins instance.
-
Inspect job configurations for custom shortcut URLsFor any existing shortcut jobs, navigate to the job configuration page and review the 'Shortcut URL' or redirection URL field to see if it contains user-supplied values.Affected if A shortcut job exists and the redirection URL field contains untrusted or externally supplied content.
You are affected if the Shortcut Job Plugin version is 0.4 or lower AND at least one shortcut job with a configured redirection URL exists in your Jenkins instance.
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 to Jenkins Shortcut Job Plugin version 0.5 or later which includes proper output encoding for the shortcut redirection URL. Until patched, restrict configuration permissions for shortcut jobs to trusted users only.
Short Job Plugin version > 0.4 (check Jenkins Plugin Index for exact latest stable release)
- Navigate to Jenkins dashboard > Manage Jenkins > Manage Plugins
- Go to the 'Installed' tab
- Locate the 'Shortcut Job' plugin in the list
- Check the current version - if it is 0.4 or earlier, an upgrade is required
- Click on the plugin and select 'Update' or upgrade via the 'Available' tab if a newer version exists
- Restart Jenkins if required after the update
- Verify the fix by testing that the shortcut redirection URL is properly escaped and no XSS can be injected
Generated from the published advisory — verify against the referenced sources before acting.
- 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-2023-40346 — 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-40346 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