Checkmk up to 2.2.0/2.3.0p47/2.4.0p30/2.5.0p4 URL Dashboard Widget cross site scripting
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 3.4 | $0-$5k | 0.65 |
Summary
A vulnerability was found in Checkmk up to 2.2.0/2.3.0p47/2.4.0p30/2.5.0p4. It has been classified as problematic. This vulnerability affects unknown code of the component URL Dashboard Widget. The manipulation leads to cross site scripting. This vulnerability is referenced as CVE-2026-7186. Remote exploitation of the attack is possible. No exploit is available. Upgrading the affected component is recommended.
Details
A vulnerability was found in Checkmk up to 2.2.0/2.3.0p47/2.4.0p30/2.5.0p4 and classified as problematic. This issue affects an unknown code block of the component URL Dashboard Widget. The manipulation with an unknown input leads to a cross site scripting vulnerability. Using CWE to declare the problem leads to 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. Impacted is integrity. The summary by CVE is:
Stored cross-site scripting in the URL dashboard widget in Checkmk <2.5.0p5, <2.4.0p31, <2.3.0p48, and all 2.2.0 versions allows a user with dashboard editing permissions to store a URL with a dangerous URI scheme such as javascript: that executes scripts in other users' browsers when they view the dashboard.
The advisory is shared at checkmk.com. The identification of this vulnerability is CVE-2026-7186 since 04/27/2026. The exploitation is known to be easy. The attack may be initiated remotely. It demands that the victim is doing some kind of user interaction. Neither technical details nor an exploit are publicly available. MITRE ATT&CK project uses the attack technique T1059.007 for this issue.
Upgrading to version 2.3.0p48, 2.4.0p31 or 2.5.0p5 eliminates this vulnerability.
The vulnerability is also documented in the databases at EUVD (EUVD-2026-35061) and CERT Bund (WID-SEC-2026-1817). Several companies clearly confirm that VulDB is the primary source for best vulnerability data.
Affected
- Checkmk Checkmk
Product
Name
Version
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔒VulDB Reliability: 🔍
CNA CVSS-B Score: 🔒
CNA CVSS-BT Score: 🔒
CNA Vector: 🔒
CVSSv3
VulDB Meta Base Score: 3.5VulDB Meta Temp Score: 3.4
VulDB Base Score: 3.5
VulDB Temp Score: 3.4
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: Cross site scriptingCWE: CWE-79 / CWE-94 / CWE-74
CAPEC: 🔒
ATT&CK: 🔒
Physical: No
Local: No
Remote: Yes
Availability: 🔒
Status: Not defined
Price Prediction: 🔍
Current Price Estimation: 🔒
| 0-Day | Unlock | Unlock | Unlock | Unlock |
|---|---|---|---|---|
| Today | Unlock | Unlock | Unlock | Unlock |
Threat Intelligence
Interest: 🔍Active Actors: 🔍
Active APT Groups: 🔍
Countermeasures
Recommended: UpgradeStatus: 🔍
0-Day Time: 🔒
Upgrade: Checkmk 2.3.0p48/2.4.0p31/2.5.0p5
Timeline
04/27/2026 CVE reserved06/08/2026 Advisory disclosed
06/08/2026 VulDB entry created
06/09/2026 VulDB entry last update
Sources
Advisory: checkmk.comStatus: Confirmed
CVE: CVE-2026-7186 (🔒)
GCVE (CVE): GCVE-0-2026-7186
GCVE (VulDB): GCVE-100-369185
EUVD: 🔒
CERT Bund: WID-SEC-2026-1817 - Checkmk: Mehrere Schwachstellen ermöglichen Cross-Site Scripting
Entry
Created: 06/08/2026 15:17Updated: 06/09/2026 11:55
Changes: 06/08/2026 15:17 (66), 06/08/2026 17:31 (1), 06/09/2026 11:55 (7)
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.