Stored XSS via unescaped build display names
Published Dec 7, 2022 · Updated Apr 23, 2025
Stored XSS in Jenkins Project Spring Config Plugin 2.0.0 and earlier allows remote authenticated users to execute scripts via build display names. SpringConfigAction/index.jelly disables default Jelly escaping and renders it.displayName as the Spring Config page title. The attacker must be able to change a build display name, and a user must open the affected view, enabling script execution in that user's browser context.
Summary
What happened
Stored XSS in Jenkins Project Spring Config Plugin 2.0.0 and earlier allows remote authenticated users to execute scripts via build display names. SpringConfigAction/index.jelly disables default Jelly escaping and renders it.displayName as the Spring Config page title. The attacker must be able to change a build display name, and a user must open the affected view, enabling script execution in that user's browser context.
The record
- CVE
- CVE-2022-46687
- Published
- Dec 7, 2022
- Updated
- Apr 23, 2025
- Vendor
- Jenkins Project
- Product
- Spring Config Plugin
- Classifications
- CWE-79, T1059.007
- Attack vector
- network
- Privileges
- authenticated
Timeline
How it unfolded
- Dec 7, 2022CVE publishedPublication date reported by the CVE source.
- Apr 23, 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.0.0
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