Stored script execution via unescaped GitHub username
Published Sep 21, 2022 · Updated May 28, 2025
Stored XSS in Jenkins DotCi Plugin 2.40.00 and earlier allows remote attackers to run script in a viewer's browser via commit notifications. The plugin stores the GitHub username from a commit notification and renders it in a build cause without escaping the value for HTML output. Exploitation requires a crafted notification to reach /githook/ and a Jenkins user to view the cause, and it applies only through Jenkins 2.314 or LTS 2.303.1.
Summary
What happened
Stored XSS in Jenkins DotCi Plugin 2.40.00 and earlier allows remote attackers to run script in a viewer's browser via commit notifications. The plugin stores the GitHub username from a commit notification and renders it in a build cause without escaping the value for HTML output. Exploitation requires a crafted notification to reach /githook/ and a Jenkins user to view the cause, and it applies only through Jenkins 2.314 or LTS 2.303.1.
The record
- CVE
- CVE-2022-41239
- Published
- Sep 21, 2022
- Updated
- May 28, 2025
- Vendor
- Jenkins Project
- Product
- DotCi
- Classifications
- CWE-79, T1203
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Sep 21, 2022CVE publishedPublication date reported by the CVE source.
- May 28, 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.40.00
What conditions does exploitation require?
What is affected?
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