CVE-2023-22309
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 · uneditedReflective Cross-Site-Scripting in Webconf in Tribe29 Checkmk Appliance before 1.6.4.
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 confidenceReflective cross-site scripting (XSS) vulnerability in the Webconf component of Tribe29 Checkmk Appliance versions prior to 1.6.4 allows unauthenticated attackers to inject malicious scripts through unsanitized user input that gets reflected back in the application's HTTP response.
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< 1.6.4CVSS 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.
-
Confirm Checkmk Appliance is runningAccess the appliance management interface or check system information. Look for 'Tribe29 Checkmk Appliance' or 'Checkmk' in the web interface footer or system dashboard.Affected if The system is not a Tribe29 Checkmk Appliance, this CVE does not apply.
-
Identify the installed firmware versionLocate the version number in the appliance's web interface (typically in the footer or 'System > Version' section) or via CLI: 'cmk -V' or check /etc/version if available on the appliance.Affected if The installed version is below 1.6.4 (e.g., 1.6.3, 1.6.0, etc.).
-
Verify Webconf component is accessibleAttempt to access the Webconf interface by navigating to the appliance's base URL or /webconf path. This is the component where the XSS vulnerability exists.Affected if The Webconf component is exposed and reachable over HTTP/HTTPS.
-
Check if the web interface reflects user input without sanitizationIf you have access, test the Webconf login or input fields by submitting a benign test string (like '<script>alert(1)</script>') in any text input and observe if it is reflected unsanitized in the response.Affected if User-supplied input is reflected back in the HTTP response without HTML encoding or sanitization.
A user is affected if they are running a Tribe29 Checkmk Appliance version prior to 1.6.4 with the Webconf component accessible, as this is where the reflective XSS vulnerability exists.
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 · scoped1.6.4
Upgrade Checkmk Appliance to version 1.6.4 or later which contains the fix for this vulnerability.
Checkmk Appliance Firmware 1.6.4
- Download the Checkmk Appliance Firmware version 1.6.4 from the official Checkmk download page
- Access the Checkmk Appliance administration interface
- Navigate to the firmware update or system upgrade section
- Upload the version 1.6.4 firmware file
- Confirm the upgrade and wait for the appliance to reboot
- Verify the upgrade was successful by checking the firmware version in the admin interface
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation3.0 h
- Implementation4.0 h
- Testing3.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 $3,408.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2023-22309 — 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-2023-22309 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