VulnSocial

CVE-2025-64999Disclosure(checkmk / checkmk)

LOWCVSS 5.4 · MEDIUM

Signal is active with 1 mentions in latest observed window

Immediate actions

  • Track advisory updates for patch or workaround availability

Recommended action window: Monitor and triage in normal cycle

NVD description

Improper neutralization of input in Checkmk versions 2.4.0 before 2.4.0p22, and 2.3.0 before 2.3.0p43 allows an attacker that can manipulate a host's check output to inject malicious JavaScript into the Synthetic Monitoring HTML logs, which can then be accessed via a crafted phishing link.

checkmk CVEsBack to dashboard
0.0/ 10 priority

Sources & remediation

Vendor / third-party advisories
Other references
Weakness type (CWE)
CWE-79

Priority

LOW

Exploitation

NONE

PoC

NONE

Patch

NONE

Momentum

NONE

Are you affected?

If you run products in this scope, you should treat this CVE as relevant to your environment.

  • checkmk

Threat summary

  • 1 mentions across 1 observed day

What's happening

  • Technical details provided in 1 signal
  • Disclosure: 1 classified signal
  • 1 total mentions across 1 day

Affected systems

Vendors
checkmk
Products
checkmk

2 versions affected across 1 product

Deep dive

Activity timeline1 mentions / 1d
00111Mentions · 2026-02-26: 1Technical Details · 2026-02-26: 102-26
Signal classification1 categories
Disclosure
1100.0%
Referenced assets1 URL
By indicator
Full discourse1 post
  • CVE@CVEnew
    Disclosure

    CVE-2025-64999 Improper neutralization of input in Checkmk versions 2.4.0 before 2.4.0p22, and 2.3.0 before 2.3.0p43 allows an attacker that can manipulate a host's check output to … https://www.cve.org/CVERecord?id=CVE-2025-64999

    Post summary

    The CVE‑2025‑64999 vulnerability involves improper input neutralization in Checkmk versions prior to 2.4.0p22 and 2.3.0p43, potentially allowing attackers to manipulate host check output.

    0000076
    56.6K followersView on X
CPE platform detail77 entries

77 of 77 entries

PartVendorProductVersionTarget SWTarget HW
Appcheckmkcheckmk2.3.0--
Appcheckmkcheckmk2.3.0--
Appcheckmkcheckmk2.3.0--
Appcheckmkcheckmk2.3.0--
Appcheckmkcheckmk2.3.0--
Appcheckmkcheckmk2.3.0--
Appcheckmkcheckmk2.3.0--
Appcheckmkcheckmk2.3.0--
Appcheckmkcheckmk2.3.0--
Appcheckmkcheckmk2.3.0--
Appcheckmkcheckmk2.3.0--
Appcheckmkcheckmk2.3.0--
Appcheckmkcheckmk2.3.0--
Appcheckmkcheckmk2.3.0--
Appcheckmkcheckmk2.3.0--
Appcheckmkcheckmk2.3.0--
Appcheckmkcheckmk2.3.0--
Appcheckmkcheckmk2.3.0--
Appcheckmkcheckmk2.3.0--
Appcheckmkcheckmk2.3.0--
Appcheckmkcheckmk2.3.0--
Appcheckmkcheckmk2.3.0--
Appcheckmkcheckmk2.3.0--
Appcheckmkcheckmk2.3.0--
Appcheckmkcheckmk2.3.0--
Appcheckmkcheckmk2.3.0--
Appcheckmkcheckmk2.3.0--
Appcheckmkcheckmk2.3.0--
Appcheckmkcheckmk2.3.0--
Appcheckmkcheckmk2.3.0--
Appcheckmkcheckmk2.3.0--
Appcheckmkcheckmk2.3.0--
Appcheckmkcheckmk2.3.0--
Appcheckmkcheckmk2.3.0--
Appcheckmkcheckmk2.3.0--
Appcheckmkcheckmk2.3.0--
Appcheckmkcheckmk2.3.0--
Appcheckmkcheckmk2.3.0--
Appcheckmkcheckmk2.3.0--
Appcheckmkcheckmk2.3.0--
Appcheckmkcheckmk2.3.0--
Appcheckmkcheckmk2.3.0--
Appcheckmkcheckmk2.3.0--
Appcheckmkcheckmk2.3.0--
Appcheckmkcheckmk2.3.0--
Appcheckmkcheckmk2.3.0--
Appcheckmkcheckmk2.3.0--
Appcheckmkcheckmk2.3.0--
Appcheckmkcheckmk2.3.0--
Appcheckmkcheckmk2.4.0--
Appcheckmkcheckmk2.4.0--
Appcheckmkcheckmk2.4.0--
Appcheckmkcheckmk2.4.0--
Appcheckmkcheckmk2.4.0--
Appcheckmkcheckmk2.4.0--
Appcheckmkcheckmk2.4.0--
Appcheckmkcheckmk2.4.0--
Appcheckmkcheckmk2.4.0--
Appcheckmkcheckmk2.4.0--
Appcheckmkcheckmk2.4.0--
Appcheckmkcheckmk2.4.0--
Appcheckmkcheckmk2.4.0--
Appcheckmkcheckmk2.4.0--
Appcheckmkcheckmk2.4.0--
Appcheckmkcheckmk2.4.0--
Appcheckmkcheckmk2.4.0--
Appcheckmkcheckmk2.4.0--
Appcheckmkcheckmk2.4.0--
Appcheckmkcheckmk2.4.0--
Appcheckmkcheckmk2.4.0--
Appcheckmkcheckmk2.4.0--
Appcheckmkcheckmk2.4.0--
Appcheckmkcheckmk2.4.0--
Appcheckmkcheckmk2.4.0--
Appcheckmkcheckmk2.4.0--
Appcheckmkcheckmk2.4.0--
Appcheckmkcheckmk2.4.0--

Explore more

Back to dashboardcheckmk CVEscheckmk vulnerabilities