Loading vulnerability…
Jenkins Coverage Plugin 2.3054.ve1ff7b_a_a_123b_ and earlier insufficiently validates the configured coverage results ID at creation time when jobs are configured via non-UI paths. While the job configuration submitted through the Jenkins UI performs validation, an attacker with Item/Configure permission can bypass this by configuring the job through the REST API and supplying a javascript: scheme URL as the coverage results identifier. When the stored identifier is later rendered in the Jenkins web UI, it can execute attacker-controlled script in victims’ browsers, resulting in stored cross-site scripting (XSS). The advisory notes this is not exploitable on Jenkins 2.539+ when Content Security Policy (CSP) protection is enforced.
Mallory correlates every CVE against your assets, your vendors, and active adversary campaigns. Know which vulnerabilities matter for you, not just which ones are loud.
What it means. What to do now. Patch path, mitigations, and the assume-compromise checklist.
What an attacker gets, and what they’ve been doing with it.
If you can’t patch tonight, do this now.
Patch, then assume compromise.
javascript: (or other dangerous) scheme identifiers.No public exploits tracked yet. Mallory keeps watching.
No public exploit code observed for this vulnerability.
Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.
Vendor-confirmed product mapping. Mallory continuously reconciles this list against your asset inventory.
7 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.
A high-severity stored XSS vulnerability in Jenkins Coverage Plugin allowing attackers with configuration permissions to inject malicious scripts into coverage reports.
A stored cross-site scripting (XSS) vulnerability in Jenkins Coverage Plugin 2.3054.ve1ff7b_a_a_123b_ and earlier allows attackers with Item/Configure permission to inject malicious JavaScript via the REST API by using a crafted coverage results ID, due to insufficient validation.
Query your assets running an affected version, and investigate the blast radius.
Every observed campaign linking this CVE to a named adversary.
Malware families riding this exploit, with evidence and IOCs.
YARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.
Cross-references every affected SKU, including bundled OEM variants.
Community discussion across Reddit, Mastodon, and other social sources.