Jenkins Coverage Plugin
Approved changes feed: RSS · Atom
cpe:2.3:a:jenkins_project:jenkins_coverage_plugin:*:*:*:*:*:*:*:*
part: a version: * update: *
| Vendor | Jenkins Project (860cd631-1316-551d-89a3-5aa9a0d4f462) |
|---|---|
| Product | Jenkins Coverage Plugin (114192c0-e18a-539f-adbe-5ec23ba2f7be) |
| Edition | * |
| Language | * |
| Software edition | * |
| Target software | * |
| Target hardware | * |
| Other | * |
| Notes | Imported from gcve-enriched-dumps CVE data |
PURL mappings
| PURL | Source | Last updated |
|---|---|---|
| No PURL mappings for this CPE yet. | ||
Vulnerability references
| Identifier | cpeApplicability | Submitted | db.gcve.eu details | Rationale |
|---|---|---|---|---|
CVE:CVE-2025-67641 |
vulnerable | 2026-06-08 07:41:20.254188 |
Details available
Jenkins Coverage Plugin 2.3054.ve1ff7b_a_a_123b_ and earlier does not validate the configured coverage results ID when creating coverage results, only when submitting the job configuration through the UI, allowing attackers with Item/Configure permission to use a `javascript:` scheme URL as identifier by configuring the job through the REST API, resulting in a stored cross-site scripting (XSS) vulnerability.
Published: 2025-12-10T16:50:39.402Z
Updated: 2025-12-10T18:16:02.206Z |
Imported from gcve-enriched-dumps CVE data |
Contribute
You can submit an edit proposal for this CPE entry or suggest a related product/vendor addition using the action button above.