BaseFortify

Publication date: 2025-12-10

Last updated on: 2025-12-17

Assigner: Jenkins Project

Description

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.

CVSS Scores

EPSS Scores

Probability:
Percentile:

Meta Information

Published

2025-12-10

Last Modified

2025-12-17

Generated

2026-07-06

AI Q&A

2025-12-10

EPSS Evaluated

2026-07-05

NVD

CVE-2025-67641

EUVD

EUVD-2025-202455

Affected Vendors & Products

Vendor	Product	Version / Range
jenkins	coverage	to 2.3054.ve1ff7b_a_a_123b (inc)

Helpful Resources

Exploitability

CWE

KEV

CWE ID	Description
CWE-79	The product does not neutralize or incorrectly neutralizes user-controllable input before it is placed in output that is used as a web page that is served to other users.

Attack-Flow Graph

Executive Summary

This vulnerability exists in Jenkins Coverage Plugin version 2.3054.ve1ff7b_a_a_123b_ and earlier. It occurs because the plugin does not validate the configured coverage results ID when creating coverage results via the REST API, only during UI job configuration submission. This allows attackers with Item/Configure permission to set a `javascript:` scheme URL as an identifier, leading to a stored cross-site scripting (XSS) vulnerability.

Impact Analysis

An attacker with Item/Configure permission can exploit this vulnerability to inject malicious JavaScript code into the Jenkins environment via the coverage results ID. This stored XSS vulnerability can lead to unauthorized script execution in the context of users viewing the affected Jenkins instance, potentially compromising user sessions, stealing credentials, or performing other malicious actions.

Hi! I’m here to help you understand CVE-2025-67641. Ask me anything about the vulnerability, its impact, or mitigation strategies.

0/70