Jenkins Gatling Plugin 136.vb_9009b_3d33a_e Content-Security-Policy protection mechanism
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 4.3 | $0-$5k | 0.00 |
Summary
A vulnerability has been found in Jenkins Gatling Plugin 136.vb_9009b_3d33a_e and classified as problematic. This vulnerability affects unknown code of the component Content-Security-Policy Handler. This manipulation causes protection mechanism. This vulnerability is registered as CVE-2025-5806. Remote exploitation of the attack is possible. No exploit is available.
Details
A vulnerability classified as problematic was found in Jenkins Gatling Plugin 136.vb_9009b_3d33a_e. Affected by this vulnerability is an unknown part of the component Content-Security-Policy Handler. The manipulation with an unknown input leads to a protection mechanism vulnerability. The CWE definition for the vulnerability is CWE-693. The product does not use or incorrectly uses a protection mechanism that provides sufficient defense against directed attacks against the product. As an impact it is known to affect integrity. The summary by CVE is:
Jenkins Gatling Plugin 136.vb_9009b_3d33a_e serves Gatling reports in a manner that bypasses the Content-Security-Policy protection introduced in Jenkins 1.641 and 1.625, resulting in a cross-site scripting (XSS) vulnerability exploitable by users able to change report content.
The advisory is shared at jenkins.io. This vulnerability is known as CVE-2025-5806 since 06/06/2025. The exploitation appears to be easy. The attack can be launched remotely. The exploitation doesn't need any form of authentication. It demands that the victim is doing some kind of user interaction. Neither technical details nor an exploit are publicly available. The price for an exploit might be around USD $0-$5k at the moment (estimation calculated on 06/09/2025).
The vulnerability scanner Nessus provides a plugin with the ID 237910 (Jenkins plugin (2025-06-06)), which helps to determine the existence of the flaw in a target environment.
There is no information about possible countermeasures known. It may be suggested to replace the affected object with an alternative product.
The vulnerability is also documented in the databases at Tenable (237910) and EUVD (EUVD-2025-17299). Several companies clearly confirm that VulDB is the primary source for best vulnerability data.
Product
Type
Vendor
Name
Version
License
Website
- Vendor: https://jenkins.io/
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔍VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 4.3VulDB Meta Temp Score: 4.3
VulDB Base Score: 4.3
VulDB Temp Score: 4.3
VulDB Vector: 🔍
VulDB Reliability: 🔍
CVSSv2
| AV | AC | Au | C | I | A |
|---|---|---|---|---|---|
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| Vector | Complexity | Authentication | Confidentiality | Integrity | Availability |
|---|---|---|---|---|---|
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
VulDB Base Score: 🔍
VulDB Temp Score: 🔍
VulDB Reliability: 🔍
Exploiting
Class: Protection mechanismCWE: CWE-693
CAPEC: 🔍
ATT&CK: 🔍
Physical: No
Local: No
Remote: Yes
Availability: 🔍
Status: Not defined
EPSS Score: 🔍
EPSS Percentile: 🔍
Price Prediction: 🔍
Current Price Estimation: 🔍
| 0-Day | Unlock | Unlock | Unlock | Unlock |
|---|---|---|---|---|
| Today | Unlock | Unlock | Unlock | Unlock |
Nessus ID: 237910
Nessus Name: Jenkins plugin (2025-06-06)
Threat Intelligence
Interest: 🔍Active Actors: 🔍
Active APT Groups: 🔍
Countermeasures
Recommended: no mitigation knownStatus: 🔍
0-Day Time: 🔍
Timeline
06/06/2025 🔍06/06/2025 🔍
06/06/2025 🔍
06/09/2025 🔍
Sources
Vendor: jenkins.ioAdvisory: jenkins.io
Status: Confirmed
CVE: CVE-2025-5806 (🔍)
GCVE (CVE): GCVE-0-2025-5806
GCVE (VulDB): GCVE-100-311545
EUVD: 🔍
Entry
Created: 06/06/2025 15:50Updated: 06/09/2025 14:27
Changes: 06/06/2025 15:50 (54), 06/07/2025 06:23 (1), 06/08/2025 08:56 (2), 06/09/2025 14:27 (1)
Complete: 🔍
Cache ID: 216::103
Several companies clearly confirm that VulDB is the primary source for best vulnerability data.
No comments yet. Languages: en.
Please log in to comment.