# CVE-2023-25762: Cross-site Scripting in Jenkins Pipeline: Build Step Plugin

> Stored XSS in Jenkins Pipeline Build Step Plugin allows attackers controlling job names to execute scripts in the Snippet Generator.

- **Severity:** Medium 5.4 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:C/C:L/I:L/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** Yes
- **Published:** 15 Feb 2023
- **Updated:** 19 Mar 2025
- **Also known as:** GHSA-9j65-3f2q-8q2r

## What is CVE-2023-25762?

CVE-2023-25762 is a medium-severity cross-site scripting vulnerability in Jenkins Pipeline: Build Step Plugin, published on 15 Feb 2023. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link.

### Official description

Jenkins Pipeline: Build Step Plugin 2.18 and earlier does not escape job names in a JavaScript expression used in the Pipeline Snippet Generator, resulting in a stored cross-site scripting (XSS) vulnerability exploitable by attackers able to control job names.

Weakness: CWE-79 (Improper Neutralization of Input During Web Page Generation)

## Which versions are affected by CVE-2023-25762?

2 open source packages ship an affected version, including org.jenkins-ci.plugins:pipeline-build-step. It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `org.jenkins-ci.plugins:pipeline-build-step` | Maven | All versions | 2.18.1 |
| `org.jenkins-ci.plugins:pipeline-build-step` | Maven | All versions | 2.18.1 |

Products: Jenkins Pipeline\.

## How do I fix CVE-2023-25762?

Upgrade org.jenkins-ci.plugins:pipeline-build-step to 2.18.1 or later.

## Is CVE-2023-25762 being exploited?

There is no known exploitation of CVE-2023-25762 in the wild and no public exploit code.

## Other vulnerabilities in Jenkins Pipeline: Build Step Plugin

- [CVE-2019-1003030](https://insights.sbomify.com/CVE-2019-1003030/): Jenkins Matrix Project Plugin Remote Code Execution (critical 9.9, exploited in the wild)
- [CVE-2022-43402](https://insights.sbomify.com/CVE-2022-43402/): Jenkins Pipeline: Groovy Plugin allows sandbox protection bypass and arbitrary code execution (critical 9.9)
- [CVE-2019-1003041](https://insights.sbomify.com/CVE-2019-1003041/): Sandbox bypass vulnerability in Jenkins Pipeline: Groovy Plugin (critical 9.8)
- [CVE-2022-43407](https://insights.sbomify.com/CVE-2022-43407/): CSRF protection for any URL can be bypassed in Jenkins Pipeline: Input Step Plugin (high 8.8)
- [CVE-2022-25173](https://insights.sbomify.com/CVE-2022-25173/): Improper Neutralization of Special Elements used in an OS Command in Jenkins Pipeline: Groovy Plugin (high 8.8)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2023-25762 and fix it if it is affected.

What it is: CVE-2023-25762 is a medium-severity cross-site scripting vulnerability in Jenkins Pipeline: Build Step Plugin, published on 15 Feb 2023. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2023-25762 in the wild and no public exploit code.

Affected packages and fixed versions:
- org.jenkins-ci.plugins:pipeline-build-step (Maven): affected all versions; fixed in 2.18.1
- org.jenkins-ci.plugins:pipeline-build-step (Maven): affected all versions; fixed in 2.18.1

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2023-25762/ (Markdown: https://insights.sbomify.com/CVE-2023-25762/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2023-25762
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2023-25762
- OSV: https://osv.dev/vulnerability/CVE-2023-25762

---
From sbomify Insights: https://insights.sbomify.com/CVE-2023-25762/
Summaries are generated and may contain mistakes; the official description above is the record.
