CVE-2024-5741
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedStored XSS in inventory tree rendering in Checkmk before 2.3.0p7, 2.2.0p28, 2.1.0p45 and 2.0.0 (EOL)
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · moderate confidenceStored cross-site scripting (XSS) vulnerability in Checkmk's inventory tree rendering component allows authenticated attackers to inject malicious JavaScript code that executes when other users view the inventory tree. The vulnerability exists in the server-side rendering of inventory data without proper output encoding.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data<= 2.0.0= 2.1.0= 2.2.0= 2.3.0CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- Low
- User interaction
- Required
- Scope
- Changed
- Confidentiality
- Low
- Integrity
- Low
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:C/C:L/I:L/A:N
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Identify installed Checkmk versionRun command 'cmk --version' or access the web UI Help > About page to view the exact version numberAffected if The version is 2.0.0 or lower, 2.1.0, 2.2.0, or 2.3.0
-
Confirm inventory tree feature is in useNavigate to the inventory tree view in the Checkmk web interface (Hosts > Inventory) to determine if this feature is actively accessed by usersAffected if The inventory tree feature is accessible and used in the environment
-
Check user access to inventory treeReview user role permissions in Checkmk at User Administration > Roles to see which roles have access to the inventory tree (cmk.inventory permission)Affected if Untrusted or unauthenticated users have access to the inventory tree viewing capability
The environment is affected if Checkmk version is 2.0.0 or lower, 2.1.0, 2.2.0, or 2.3.0 AND the inventory tree feature is accessible to users who are not trusted to inject malicious scripts.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
dbcve · scopedUpgrade Checkmk to version 2.3.0p7, 2.2.0p28, 2.1.0p45, or later. Alternatively, restrict access to the inventory tree feature to trusted users only until patching is possible.
2.3.0p7 (for 2.3.x), 2.2.0p28 (for 2.2.x), or 2.1.0p45 (for 2.1.x) - Note: 2.0.0 is End-of-Life with no patch available
- Identify the current Checkmk version running in your environment
- Determine the appropriate upgrade path based on your current version branch (2.0.x, 2.1.x, 2.2.x, or 2.3.x)
- Backup the current Checkmk installation and configuration data
- Download the fixed patch version from Checkmk: 2.3.0p7 for 2.3.x branch, 2.2.0p28 for 2.2.x branch, 2.1.0p45 for 2.1.x branch
- Follow Checkmk official upgrade documentation to apply the patch
- Restart the Checkmk services after upgrade
- Verify the upgrade was successful by checking the version and that the inventory tree functionality works correctly
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation3.0 h
- Implementation3.0 h
- Testing2.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,880.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-5741 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2024-5741 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data