Jenkins Pipeline: Job Plugin vulnerable to stored Cross-site Scripting

Exploitation

No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.

CVSS

7.5 · CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:H

EPSS

• CVE-2023-32977: 0.59% estimated exploitation activity in the next 30 days; percentile 48.04 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.

As published by the source; long descriptions are shortened.

Jenkins Pipeline: Job Plugin 1292.v27d8cc3e2602 and earlier does not escape the display name of the build that caused an earlier build to be aborted, when "Do not allow concurrent builds" is set. This results in a stored cross-site scripting (XSS) vulnerability exploitable by attackers able to set build display names immediately. The Jenkins security team is not aware of any plugins that allow the exploitation of this vulnerability, as the build name must be set before the build starts. Pipeline: Job Plugin 1295.v395eb7400005 escapes the display name of the build that caused an earlier build to be aborted.

Published by the source

16 May 2023, 18:30 UTC

Last modified by the source

4 Jan 2024, 12:03 UTC

Source last checked

26 Oct 2026, 16:24 UTC

1. Revision 1 · created · 26 Oct 2026

   Published from ghsa record GHSA-2wvv-phhw-qvmc

Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.

# Patch Next advisory brief: CVE-2023-32977

Advisory: Jenkins Pipeline: Job Plugin vulnerable to stored Cross-site Scripting
IDs: CVE-2023-32977, GHSA-2wvv-phhw-qvmc
Record: https://patchnext.com/advisories/cve-2023-32977 (revision 1, source checked 26 Oct 2026, 16:24 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: High (CVSS 7.5)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor fix available; fixed versions by package: org.jenkins-ci.plugins.workflow:workflow-job 1295.v395eb. A vendor fix does not mean a deployment is fixed.

## Affected components
- Maven org.jenkins-ci.plugins.workflow:workflow-job: affected < 1295.v395eb; fixed in 1295.v395eb

## Suggested inspection (read-only)
- Maven org.jenkins-ci.plugins.workflow:workflow-job: check the installed version with your package manager.

## Supported action
Upgrade each affected component to a fixed version on its release line. For a transitive dependency, upgrade the parent package or add an override or constraint, then regenerate the lockfile. Redeploy every environment that ran an affected version.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on org.jenkins-ci.plugins.workflow:workflow-job.
- Repeat the inspection and confirm that only fixed versions remain installed.

## Rollback considerations
- Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward.

## Unresolved questions
- Which deployments run an affected version?
- Exploitation status can change. Check again before lowering the priority.
- Mark the work resolved only after the fixed version is verified in production.

## Sources
- Verified: https://github.com/advisories/GHSA-2wvv-phhw-qvmc (GitHub-reviewed advisory GHSA-2wvv-phhw-qvmc lists affected ranges: Maven org.jenkins-ci.plugins.workflow:workflow-job >=0 <1295.v395eb)

Commands are suggestions: review each one before running it.