dbcve.org
CheckmkApplication

CVE-2024-6052

MEDIUM · 5.4 CVSS v3.1 Published 2024-07-03
Fix available
A fix is available. Upgrade to after 2.0.0 or later.
See remediation →
58/100
Remediation priority · Elevated
Remotely reachable

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 · unedited
Stored XSS in Checkmk before versions 2.3.0p8, 2.2.0p29, 2.1.0p45, and 2.0.0 (EOL) allows users to execute arbitrary scripts by injecting HTML elements

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 confidence

Stored cross-site scripting (XSS) vulnerability in Checkmk allows authenticated users to inject malicious HTML/JavaScript code into input fields. The injected payload is stored on the server and executes when other users view the affected content, enabling session hijacking, credential theft, or malicious actions in the context of victim users.

MitigationUpgrade Checkmk to version 2.3.0p8, 2.2.0p29, 2.1.0p45 or later. If upgrading is not immediately possible, implement input validation and output encoding on user-supplied fields as a compensating control.

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
CheckmkApplication
Affected:<= 2.0.0= 2.1.0= 2.2.0= 2.3.0

CVSS 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 checks

Work through these to decide whether this CVE applies to you.

  1. Determine installed Checkmk version
    Run the command 'cmk --version' or check the Checkmk web interface footer for the version number, or look in /omd/sites/<site>/etc/version
    Affected if The installed version is 2.0.0 or lower, 2.1.0, 2.2.0, or 2.3.0 (any version listed as affected)
  2. Verify Checkmk web interface is active
    Access the Checkmk web interface URL and confirm you can log in as an authenticated user
    Affected if The web interface is accessible and you have an authenticated session, allowing you to test input fields
  3. Identify input fields that accept user data
    Navigate to Checkmk configuration areas such as host properties, contact definitions, notification rules, or custom macros where user input is collected and stored
    Affected if Input fields exist that accept and store user-supplied data without proper sanitization
  4. Search for existing malicious payloads in stored data
    Query the Checkmk database (typically in /omd/sites/<site>/var/nagios/rw/nagios.qh or through the web interface) for suspicious HTML tags, script tags, or JavaScript event handlers in stored configuration values
    Affected if Any stored configuration values contain unescaped HTML or JavaScript code that could execute in another user's browser

You are affected if your Checkmk version is 2.0.0 or lower, 2.1.0, 2.2.0, or 2.3.0 and you have authenticated users who can access input fields that store and display user-supplied content without sanitization.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 · scoped
Upgrade available Upgrade to a release after 2.0.0
Interim mitigation

Upgrade Checkmk to version 2.3.0p8, 2.2.0p29, 2.1.0p45 or later. If upgrading is not immediately possible, implement input validation and output encoding on user-supplied fields as a compensating control.

Recommended fix High confidence

2.3.0p8 (for 2.3.x), 2.2.0p29 (for 2.2.x), or 2.1.0p45 (for 2.1.x) - Note: 2.0.0 is End-of-Life and no patch is available

  1. 1. Identify your current Checkmk version by checking the about page or running 'cmk --version'
  2. 2. Based on your current major version (2.0.0, 2.1.0, 2.2.0, or 2.3.0), plan upgrade to the corresponding fixed patch version
  3. 3. Back up your Checkmk configuration and data before proceeding with the upgrade
  4. 4. Download the appropriate fixed patch version from checkmk.com (2.3.0p8, 2.2.0p29, or 2.1.0p45)
  5. 5. Follow Checkmk's standard upgrade procedure to apply the patch
  6. 6. Verify the upgrade was successful and the XSS vulnerability is patched
Caveat No breaking changes expected for patch-level upgrades; however, if upgrading across major versions, review Checkmk migration notes

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Checkmk Scoped from the published advisory
  • Consultation4.0 h
  • Implementation4.0 h
  • Testing6.0 h
  • Review / QA3.0 h
17.0 hours of engineering $2,960
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,736.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2024-6052 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2024-6052 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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