Home
» Security vulnerabilities
» CVE-2024-2380
Stored XSS in graph rendering in Checkmk <2.3.0b4.
NVD Status: Analyzed ,CVE State: published
Threat Intelligence & Risk Assessment for CVE-2024-2380
Conclusion & alert: CVE-2024-2380 is rated Low Risk (27.1/100) : CVSS Medium severity, with low exploitation likelihood (EPSS 0.34%). Mandatory action: Monitor for updates and reassess as exploit intelligence or EPSS changes.
Risk is dynamic; we continuously reassess and refresh what is shown on this page as upstream context changes.
Exploit prediction scoring system (EPSS) score for CVE-2024-2380
EPSS lead: Daily EPSS estimates relative likelihood of exploitation; percentile ranks this CVE among scored vulnerabilities (higher = more severe relative rank).
#
Date
Old EPSS score
New EPSS score
Delta (New - Old)
1
2026-06-15
0.80%
0.34%
-0.46%
2
2025-11-21
0.50%
0.80%
+0.30%
3
2025-11-18
—
0.50%
—
Full EPSS history
(10 records total)
Common vulnerability scoring system (CVSS) metrics for CVE-2024-2380
CVSS metrics for this CVE.
Base score
Version
Severity
Vector
Exploitability
Impact
Score source
4.6
3.1
MEDIUM
CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:U/C:L/I:L/A:N
Click to expand
Attack vector (AV:N)
Could be attacked over the internet or any normal routed network—not just someone sitting at the machine.
Attack complexity (AC:L)
Once they can reach the bug, pulling it off is straightforward—no weird race conditions or rare setup.
Privileges required (PR:L)
A normal user session is enough; they don’t have to be admin.
User interaction (UI:R)
A real person has to do something—click, install, enable—otherwise it doesn’t land.
Scope (S:U)
Damage stays in the same “trust bubble” as the broken component—no big spill into unrelated systems.
Confidentiality (C:L)
Some sensitive info could get out, but not a total data dump.
Integrity (I:L)
Attackers could change some data, but it’s limited—not everything goes.
Availability (A:N)
Service keeps running; no real outage angle.
2.1
2.5
[email protected]
5.4
3.1
MEDIUM
CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:C/C:L/I:L/A:N
Click to expand
Attack vector (AV:N)
Could be attacked over the internet or any normal routed network—not just someone sitting at the machine.
Attack complexity (AC:L)
Once they can reach the bug, pulling it off is straightforward—no weird race conditions or rare setup.
Privileges required (PR:L)
A normal user session is enough; they don’t have to be admin.
User interaction (UI:R)
A real person has to do something—click, install, enable—otherwise it doesn’t land.
Scope (S:C)
Breaking this can reach past the original component and bite other resources—bigger blast radius.
Confidentiality (C:L)
Some sensitive info could get out, but not a total data dump.
Integrity (I:L)
Attackers could change some data, but it’s limited—not everything goes.
Availability (A:N)
Service keeps running; no real outage angle.
2.3
2.7
[email protected]
Weakness enumeration for CVE-2024-2380
OS Trackers for CVE-2024-2380
vendor
priority
summary
link
ubuntu
medium
CVE-2024-2380 medium priority: Ubuntu including 1 source packages (check-mk), 10 status rows across 10 suites (bionic, focal, jammy, mantic, noble, oracular, plucky, questing, upstream, xenial): DNE 7, needs-triage 3.
https://ubuntu.com/security/CVE-2024-2380
Affected software / configurations for CVE-2024-2380
Vendor
Product
Version
Raw CPE
checkmk
checkmk
2.3.0
cpe:2.3:a:checkmk:checkmk:2.3.0:b1:*:*:*:*:*:*
checkmk
checkmk
2.3.0
cpe:2.3:a:checkmk:checkmk:2.3.0:b2:*:*:*:*:*:*
checkmk
checkmk
2.3.0
cpe:2.3:a:checkmk:checkmk:2.3.0:b3:*:*:*:*:*:*
References for CVE-2024-2380
cvelogic
Threat Intelligence