CVE-2024-38860
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 · uneditedImproper neutralization of input in Checkmk before versions 2.3.0p16 and 2.2.0p34 allows attackers to craft malicious links that can facilitate phishing attacks.
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 confidenceImproper neutralization of input in Checkmk before versions 2.3.0p16 and 2.2.0p34 allows attackers to craft malicious links. This is a cross-site scripting (XSS) vulnerability where user-supplied input is not properly sanitized, enabling attackers to inject malicious scripts or conduct phishing attacks via crafted URLs.
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.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
- None
- User interaction
- Required
- Scope
- Changed
- Confidentiality
- Low
- Integrity
- Low
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/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.
-
Determine installed Checkmk versionRun command: 'cmk --version' or 'check_mk --version' on the Checkmk server. Alternatively, check /omd/sites/<sitename>/version if using OMD/omd installation.Affected if Version is 2.2.0 up to 2.2.0p33, or 2.3.0 up to 2.3.0p15 (the vulnerable versions before the patches)
-
Confirm Checkmk web interface is enabledCheck if the web service is running: 'omd status <sitename>' or look for apache/nginx processes serving the Checkmk web interface.Affected if The web interface is active and accessible (required for the XSS attack vector)
-
Identify the specific patch version installedIf running 2.2.0 or 2.3.0 base version, check the exact patch level via 'cmk --version' output or the Checkmk web interface about page.Affected if Patch level is below p16 for 2.3.x or below p34 for 2.2.x
You are affected if your Checkmk installation runs version 2.2.0 through 2.2.0p33 or 2.3.0 through 2.3.0p15 and has the web interface enabled, as these versions contain the unsanitized input in link rendering.
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.0p16 or 2.2.0p34 or later to obtain the patch for this vulnerability.
Upgrade to Checkmk 2.2.0p34 (for 2.2.x users) or 2.3.0p16 (for 2.3.x users)
- 1. Identify your current Checkmk version by running `cmk --version` or checking the GUI footer
- 2. Determine which upgrade path suits your environment: upgrade to 2.2.0p34 (if on 2.2.x line) or 2.3.0p16 (if on 2.3.x line)
- 3. Create a full backup of your Checkmk installation, including the site directory (typically /opt/omd/sites/<sitename>)
- 4. Review Checkmk upgrade documentation for your current version at checkmk.com/download
- 5. Download the appropriate patched version (2.2.0p34 or 2.3.0p16) from the Checkmk download page
- 6. Stop the Checkmk site before upgrade: `cmk -S` or `omd stop <sitename>`
- 7. Install the patched version following Checkmk's standard upgrade procedure
- 8. Start the site after upgrade: `omd start <sitename>`
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation4.0 h
- Testing6.0 h
- Review / QA3.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,096.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-38860 — 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-38860 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