Stored XSS via unescaped legacy wrapper metadata
Published Apr 29, 2026 · Updated Apr 29, 2026
Stored XSS in Jenkins Project HTML Publisher Plugin 427 and earlier allows remote authenticated users to run script via published reports. The legacy wrapper generator inserts the configured job name and URL into HTML without escaping them, preserving attacker-controlled markup in generated wrapper files. Item/Configure permission and a viewer opening an affected wrapper are required; the script runs in the Jenkins origin with the viewer's privileges.
Summary
What happened
Stored XSS in Jenkins Project HTML Publisher Plugin 427 and earlier allows remote authenticated users to run script via published reports. The legacy wrapper generator inserts the configured job name and URL into HTML without escaping them, preserving attacker-controlled markup in generated wrapper files. Item/Configure permission and a viewer opening an affected wrapper are required; the script runs in the Jenkins origin with the viewer's privileges.
The record
- CVE
- CVE-2026-42524
- Published
- Apr 29, 2026
- Updated
- Apr 29, 2026
- Vendor
- Jenkins Project
- Product
- HTML Publisher Plugin
- Classifications
- CWE-79, T1059.007
- Attack vector
- network
- Privileges
- authenticated
Timeline
How it unfolded
- Apr 29, 2026CVE publishedPublication date reported by the CVE source.
- Apr 29, 2026Record 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 <=427
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