Stored XSS via unescaped job names
Published Feb 15, 2023 · Updated Mar 19, 2025
Stored XSS in Jenkins Pipeline: Build Step Plugin 2.18 and earlier allows remote authenticated users to execute script via job names. The BuildTriggerStep configuration view inserts the job context into an Ajax Request JavaScript expression without JavaScript escaping. Exploitation requires control of a job name and a user to open the affected Pipeline Snippet Generator; the injected script runs in that user's browser.
Summary
What happened
Stored XSS in Jenkins Pipeline: Build Step Plugin 2.18 and earlier allows remote authenticated users to execute script via job names. The BuildTriggerStep configuration view inserts the job context into an Ajax Request JavaScript expression without JavaScript escaping. Exploitation requires control of a job name and a user to open the affected Pipeline Snippet Generator; the injected script runs in that user's browser.
The record
- CVE
- CVE-2023-25762
- Published
- Feb 15, 2023
- Updated
- Mar 19, 2025
- Vendor
- Jenkins Project
- Product
- Pipeline: Build Step Plugin
- Classifications
- CWE-79, T1203
- Attack vector
- network
- Privileges
- authenticated
Timeline
How it unfolded
- Feb 15, 2023CVE publishedPublication date reported by the CVE source.
- Mar 19, 2025Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=unspecified <=2.18
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo