Jenkins Coverage Plugin XSS via REST API ID unvalidated (before 2.3054)
CVE-2025-67641 Published on December 10, 2025

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.

Vendor Advisory NVD

Vulnerability Analysis

CVE-2025-67641 can be exploited with network access, requires user interaction and a small amount of user privileges. This vulnerability is considered to have a low attack complexity. The potential impact of an exploit of this vulnerability is considered to be very high.

Attack Vector:
NETWORK
Attack Complexity:
LOW
Privileges Required:
LOW
User Interaction:
REQUIRED
Scope:
UNCHANGED
Confidentiality Impact:
HIGH
Integrity Impact:
HIGH
Availability Impact:
HIGH

Weakness Type

What is a XSS Vulnerability?

The software 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.

CVE-2025-67641 has been classified to as a XSS vulnerability or weakness.


Products Associated with CVE-2025-67641

Want to know whenever a new CVE is published for Jenkins? stack.watch will email you.

 

Affected Versions

Jenkins Project Jenkins Coverage Plugin:

Exploit Probability

EPSS
0.04%
Percentile
13.30%

EPSS (Exploit Prediction Scoring System) scores estimate the probability that a vulnerability will be exploited in the wild within the next 30 days. The percentile shows you how this score compares to all other vulnerabilities.