dbcve.org
CheckmkApplication

CVE-2023-23548

MEDIUM · 6.1 CVSS v3.1 Published 2023-08-01
Fix available
A fix is available. Upgrade to after 1.6.0 or later.
See remediation →
68/100
Remediation priority · Elevated
Remotely reachable No privileges

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
Reflected XSS in business intelligence in Checkmk <2.2.0p8, <2.1.0p32, <2.0.0p38, <=1.6.0p30.

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 · high confidence

Reflected Cross-Site Scripting (XSS) vulnerability in Checkmk's business intelligence component allows attackers to inject malicious scripts via unsanitized user input that gets reflected in the response. The attack requires tricking a user into clicking a specially crafted URL.

MitigationUpgrade Checkmk to version 2.2.0p8, 2.1.0p32, 2.0.0p38, or 1.6.0p31 or later. As a temporary workaround, disable or restrict access to the business intelligence feature until the patch can be applied.

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:<= 1.6.0= 2.0.0= 2.1.0= 2.2.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
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 checks

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

  1. Check installed Checkmk version
    Access the Checkmk web interface and navigate to the version information page, typically found under 'Help' > 'About Checkmk' or by running 'omd version' command on the server if you have CLI access
    Affected if The installed version is 1.6.0 or lower, 2.0.0, 2.1.0, or 2.2.0 exactly
  2. Verify business intelligence feature is enabled
    Log into the Checkmk web interface and navigate to the Business Intelligence (BI) section, typically found under 'Business Intelligence' in the main navigation menu
    Affected if The BI module is accessible and visible in the web interface, indicating it is enabled
  3. Confirm BI pack access for users
    Check user permissions by navigating to 'Users' > 'Roles and permissions' in Checkmk and verify if the 'Business Intelligence' permission is granted to any active user role
    Affected if Users have permission to access the Business Intelligence feature, making the reflected XSS vector accessible

You are affected if your Checkmk version is 1.6.0 or lower, 2.0.0, 2.1.0, or 2.2.0 AND the Business Intelligence feature is enabled and accessible to users in your environment.

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 1.6.0
Interim mitigation

Upgrade Checkmk to version 2.2.0p8, 2.1.0p32, 2.0.0p38, or 1.6.0p31 or later. As a temporary workaround, disable or restrict access to the business intelligence feature until the patch can be applied.

Recommended fix High confidence

1.6.0p31 (for 1.6.x), 2.0.0p38 (for 2.0.x), 2.1.0p32 (for 2.1.x), or 2.2.0p8 (for 2.2.x)

  1. 1. Identify your current Checkmk version using 'cmk --version' or the web interface Help > About section.
  2. 2. Based on your current major version, plan to upgrade to the minimum patched release: For 1.6.0 users: upgrade to 1.6.0p31 or later; For 2.0.0 users: upgrade to 2.0.0p38 or later; For 2.1.0 users: upgrade to 2.1.0p32 or later; For 2.2.0 users: upgrade to 2.2.0p8 or later.
  3. 3. Review Checkmk upgrade documentation for your specific version at checkmk.com/download.
  4. 4. Before upgrading in production, test the upgrade in a staging environment to verify compatibility with your monitoring configurations.
  5. 5. Perform a full backup of your Checkmk site(s) and configuration data.
  6. 6. Apply the upgrade following Checkmk's standard upgrade procedure (omd upgrade or site-specific method).
  7. 7. After upgrade, verify the BI (Business Intelligence) functionality works correctly and confirm the version has been updated.
Caveat Minor: Patch releases typically contain bug fixes and security patches without major functionality changes; however, always review the changelog for any configuration adjustments needed

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

Fix this in Checkmk Scoped from the published advisory
  • Consultation2.0 h
  • Implementation2.0 h
  • Testing3.0 h
  • Review / QA1.0 h
8.0 hours of engineering $1,390
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2023-23548 — 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-2023-23548 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