dbcve.org
GitHubApplication · Jenkins

CVE-2023-46650

MEDIUM · 5.4 CVSS v3.1 Published 2023-10-25
Fix available
A fix is available. Upgrade to after 1.37.3 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 GitHub Plugin 1.37.3 and earlier does not escape the GitHub project URL on the build page when showing changes, resulting in a stored cross-site scripting (XSS) vulnerability exploitable by attackers with Item/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 confidence

The Jenkins GitHub Plugin versions 1.37.3 and earlier fail to properly escape the GitHub project URL when displaying changes on the build page, allowing stored XSS attacks. Attackers with Item/Configure permission can inject malicious scripts via the GitHub project URL that will execute in the browsers of users viewing the build changes.

MitigationUpdate Jenkins GitHub Plugin to version 1.37.4 or later which includes proper output encoding. Alternatively, restrict Item/Configure permission to trusted users only until the patch can be applied.

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
GitHubApplication
Affected:<= 1.37.3

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 Jenkins GitHub Plugin is installed
    Navigate to Manage Jenkins > Manage Plugins > Installed tab and locate the GitHub plugin in the list
    Affected if The GitHub plugin appears in the installed plugins list
  2. Check the installed version of the GitHub Plugin
    In the plugin manager Installed tab, find the GitHub plugin and note the version number shown in the Version column
    Affected if The installed version is 1.37.3 or any earlier version (e.g., 1.37.2, 1.37.1, 1.37.0, etc.)
  3. Identify jobs with GitHub project URL configured
    Review job configurations: for each job, go to Configure > General section and check if the 'GitHub project' checkbox is enabled with a URL entered in the 'Project URL' field
    Affected if Any job has a GitHub project URL configured (this is the data that gets improperly escaped)
  4. Review who has Item/Configure permission
    Check job-level permissions: go to job > Configure > Enable project-based security and review which users or groups have the Configure permission, or check overall Manage Jenkins > Manage Users for user accounts
    Affected if There are users with Item/Configure permission who are not fully trusted (these users can inject the malicious URL)

You are affected if the GitHub Plugin version is 1.37.3 or earlier AND at least one job has a GitHub project URL configured AND untrusted users have Item/Configure permission.

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 1.37.3
Interim mitigation

Update Jenkins GitHub Plugin to version 1.37.4 or later which includes proper output encoding. Alternatively, restrict Item/Configure permission to trusted users only until the patch can be applied.

Recommended fix Moderate confidence

GitHub Plugin version 1.37.4 or later

  1. 1. Navigate to Jenkins dashboard
  2. 2. Go to Manage Jenkins > Manage Plugins
  3. 3. Click on the 'Updates' tab
  4. 4. Find the GitHub Plugin in the list
  5. 5. Select the GitHub Plugin and click 'Download now and install after restart'
  6. 6. Wait for the plugin to download and install
  7. 7. Restart Jenkins to complete the upgrade

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in GitHub Scoped from the published advisory
  • Consultation3.0 h
  • Implementation4.0 h
  • Testing4.0 h
  • Review / QA2.0 h
13.0 hours of engineering $2,280
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,648.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2023-46650 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

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-46650 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