Stored XSS via unescaped view names
Published Mar 6, 2024 · Updated Mar 27, 2025
Stored XSS in Jenkins Build Monitor View Plugin 1.14-860.vd06ef2568b_3f and earlier allows remote authenticated users to run browser scripts. The plugin renders attacker-controlled Build Monitor View names without output escaping, causing browsers to interpret embedded markup as active content. The attacker must be able to configure Build Monitor Views, and exploitation requires another user to load an affected view.
Summary
What happened
Stored XSS in Jenkins Build Monitor View Plugin 1.14-860.vd06ef2568b_3f and earlier allows remote authenticated users to run browser scripts. The plugin renders attacker-controlled Build Monitor View names without output escaping, causing browsers to interpret embedded markup as active content. The attacker must be able to configure Build Monitor Views, and exploitation requires another user to load an affected view.
The record
- CVE
- CVE-2024-28156
- Published
- Mar 6, 2024
- Updated
- Mar 27, 2025
- Vendor
- Jenkins Project
- Product
- Jenkins Build Monitor Plugin
- Classifications
- CWE-79, T1059.007
- Attack vector
- network
- Privileges
- authenticated
Timeline
How it unfolded
- Mar 6, 2024CVE publishedPublication date reported by the CVE source.
- Mar 27, 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=0 <=1.14-860.vd06ef2568b_3f
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