Shortcut JobApplication · Jenkins

CVE-2023-40346

MEDIUM · 5.4 CVSS v3.1 Published 2023-08-16
Fix available
A fix is available. Upgrade to after 0.4 or later.
See remediation →
58/100
Remediation priority · Elevated
Remotely reachable

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 · unedited
Jenkins 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 confidence

The 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.

MitigationUpgrade 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.

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
Shortcut JobApplication
Affected:<= 0.4

CVSS 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 checks

Work through these to decide whether this CVE applies to you.

  1. Verify the Shortcut Job Plugin is installed
    Navigate 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.
  2. Determine the installed version of the Shortcut Job Plugin
    In 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).
  3. Check if shortcut jobs exist in the system
    Use 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.
  4. Inspect job configurations for custom shortcut URLs
    For 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.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 · scoped
Upgrade available Upgrade to a release after 0.4
Interim mitigation

Upgrade 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.

Recommended fix Moderate confidence

Short Job Plugin version > 0.4 (check Jenkins Plugin Index for exact latest stable release)

  1. Navigate to Jenkins dashboard > Manage Jenkins > Manage Plugins
  2. Go to the 'Installed' tab
  3. Locate the 'Shortcut Job' plugin in the list
  4. Check the current version - if it is 0.4 or earlier, an upgrade is required
  5. Click on the plugin and select 'Update' or upgrade via the 'Available' tab if a newer version exists
  6. Restart Jenkins if required after the update
  7. 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.

Fix this in Shortcut Job Scoped from the published advisory
  • Consultation1.0 h
  • Implementation2.0 h
  • Testing2.0 h
  • Review / QA1.0 h
6.0 hours of engineering $1,040
Get the upgrade done

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 locally
dbcve dependency scanner

Check 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 sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2023-40346 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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