Stored XSS via unescaped report metadata
Published Mar 6, 2024 · Updated Mar 25, 2025
Stored XSS in Jenkins OWASP Dependency-Check Plugin 5.4.5 and earlier allows attackers to run script in report viewers' browsers. FindingsTransformer inserted vulnerability names, descriptions, dependency fields, and references into findings-table JSON without HTML escaping. Exploitation requires control of workspace contents or CVE metadata and a user viewing the report, enabling actions within that viewer's Jenkins session.
Summary
What happened
Stored XSS in Jenkins OWASP Dependency-Check Plugin 5.4.5 and earlier allows attackers to run script in report viewers' browsers. FindingsTransformer inserted vulnerability names, descriptions, dependency fields, and references into findings-table JSON without HTML escaping. Exploitation requires control of workspace contents or CVE metadata and a user viewing the report, enabling actions within that viewer's Jenkins session.
The record
- CVE
- CVE-2024-28153
- Published
- Mar 6, 2024
- Updated
- Mar 25, 2025
- Vendor
- Jenkins Project
- Product
- OWASP Dependency-Check Jenkins Plugin
- Classifications
- CWE-79, CAPEC-592, T1189
- Attack vector
- network
- Privileges
- authenticated
Timeline
How it unfolded
- Mar 6, 2024CVE publishedPublication date reported by the CVE source.
- Mar 25, 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 <=5.4.5
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