Skip to main content
VulnerabilityPublished

CVE-2026-125363: SecOps-7 MikroDash · Server-Side Request Forgery (SSRF)

Affects SecOps-7 MikroDashSource CVE Database V5

0
Compare

Not known to be exploited · CVSS 5.3 Medium : upgrade to 0.8.79 when convenient.

Data as of 10 Nov 2026, 00:03 UTC

CVSS 4.0 base score
5.3Medium
How severe the flaw is on the 0–10 CVSS scale.

Thin evidence

One scorer or none
CVSS scores by source
CNA (VulnCheck)CVSS 4.05.3
CNA (VulnCheck)CVSS 3.15.4
Patch
Available – fixed in 0.8.79
CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:L/VI:L/VA:N/SC:N/SI:N/SA:N

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 9 Nov 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 9 Nov 2026.

What to do

Upgrade SecOps-7 MikroDash to 0.8.79.

Affected software

ProductAffectedFixed in
SecOps-7MikroDashAffected
  • <0.8.79
Fixed in
  • 0.8.79
GitHubMikroDashpkg:github/MikroDashOther threatsAffected
  • <0.8.79
Fixed in
  • 0.8.79

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

Upgrade MikroDash to version 0.8.79 or later, where this SSRF vulnerability is fixed. There are no vendor advisories indicating alternative mitigations or that no action is required. Applying the official fix is the recommended remediation.

Description

MikroDash versions before 0.8.79 contain a server-side request forgery (SSRF) vulnerability. This flaw allows any signed-in user, including those with viewer role permissions, to send crafted requests targeting internal network addresses via notification channels. Attackers can configure webhook or mail destinations to internal IP ranges such as loopback, LAN, or link-local addresses and use the POST /api/notify-channels/{id}/test endpoint to probe internal systems.

References

Community reviews

Loading reviews…