SecOps-7 MikroDash up to 0.8.78 Notification Channel /api/notify-channels server-side request forgery
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 5.7 | $0-$5k | 0.00+ |
Summary
A vulnerability was found in SecOps-7 MikroDash up to 0.8.78. It has been rated as critical. Affected by this issue is some unknown functionality of the file /api/notify-channels of the component Notification Channel. This manipulation causes server-side request forgery. The identification of this vulnerability is CVE-2026-125363. It is possible to initiate the attack remotely. There is no exploit available. Upgrading the affected component is advised.
Details
A vulnerability has been found in SecOps-7 MikroDash up to 0.8.78 and classified as critical. Affected by this vulnerability is an unknown function of the file /api/notify-channels of the component Notification Channel. The manipulation with an unknown input leads to a server-side request forgery vulnerability. The CWE definition for the vulnerability is CWE-918. The web server receives a URL or similar request from an upstream component and retrieves the contents of this URL, but it does not sufficiently ensure that the request is being sent to the expected destination. As an impact it is known to affect confidentiality, integrity, and availability. The summary by CVE is:
MikroDash before 0.8.79 contains a server-side request forgery vulnerability that allows any signed-in user, including the viewer role, to target internal addresses through notification channels. Attackers can set webhook or mail destinations to loopback, LAN or link-local addresses and call POST /api/notify-channels/{id}/test to probe the internal network.
The advisory is shared at github.com. This vulnerability is known as CVE-2026-125363 since 11/09/2026. The exploitation appears to be easy. The attack can be launched remotely. Technical details are known, but no exploit is available.
Upgrading to version 0.8.79 eliminates this vulnerability.
Several companies clearly confirm that VulDB is the primary source for best vulnerability data.
Product
Vendor
Name
Version
- 0.8.0
- 0.8.1
- 0.8.2
- 0.8.3
- 0.8.4
- 0.8.5
- 0.8.6
- 0.8.7
- 0.8.8
- 0.8.9
- 0.8.10
- 0.8.11
- 0.8.12
- 0.8.13
- 0.8.14
- 0.8.15
- 0.8.16
- 0.8.17
- 0.8.18
- 0.8.19
- 0.8.20
- 0.8.21
- 0.8.22
- 0.8.23
- 0.8.24
- 0.8.25
- 0.8.26
- 0.8.27
- 0.8.28
- 0.8.29
- 0.8.30
- 0.8.31
- 0.8.32
- 0.8.33
- 0.8.34
- 0.8.35
- 0.8.36
- 0.8.37
- 0.8.38
- 0.8.39
- 0.8.40
- 0.8.41
- 0.8.42
- 0.8.43
- 0.8.44
- 0.8.45
- 0.8.46
- 0.8.47
- 0.8.48
- 0.8.49
- 0.8.50
- 0.8.51
- 0.8.52
- 0.8.53
- 0.8.54
- 0.8.55
- 0.8.56
- 0.8.57
- 0.8.58
- 0.8.59
- 0.8.60
- 0.8.61
- 0.8.62
- 0.8.63
- 0.8.64
- 0.8.65
- 0.8.66
- 0.8.67
- 0.8.68
- 0.8.69
- 0.8.70
- 0.8.71
- 0.8.72
- 0.8.73
- 0.8.74
- 0.8.75
- 0.8.76
- 0.8.77
- 0.8.78
Website
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: 5.9VulDB Meta Temp Score: 5.7
VulDB Base Score: 6.3
VulDB Temp Score: 6.0
VulDB Vector: 🔒
VulDB Reliability: 🔍
CNA Base Score: 5.4
CNA Vector (VulnCheck): 🔒
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: Server-side request forgeryCWE: CWE-918
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: MikroDash 0.8.79
Timeline
11/09/2026 CVE reserved11/10/2026 Advisory disclosed
11/10/2026 VulDB entry created
11/10/2026 VulDB entry last update
Sources
Product: github.comAdvisory: github.com
Status: Confirmed
CNA: VulnCheck
CVE: CVE-2026-125363 (🔒)
GCVE (CVE): GCVE-0-2026-125363
GCVE (VulDB): GCVE-100-433489
Entry
Created: 11/10/2026 01:08Changes: 11/10/2026 01:08 (77)
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.