CVE-2025-58121
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 · uneditedInsufficient permission validation on multiple REST API endpoints in Checkmk 2.2.0, 2.3.0, and 2.4.0 before version 2.4.0p16 allows low-privileged users to perform unauthorized actions or obtain sensitive information
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 confidenceInsufficient permission validation on multiple REST API endpoints in Checkmk allows low-privileged users to bypass authorization checks and perform actions or access data intended for higher-privilege users. This represents a broken access control vulnerability in the API layer.
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.4.0= 2.4.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
- None
- Scope
- Unchanged
- Confidentiality
- Low
- Integrity
- Low
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/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: omd version or check the Checkmk web interface footer for the version numberAffected if Version is >= 2.2.0 and < 2.4.0, or exactly 2.4.0 (any patch version before 2.4.0p16)
-
Verify REST API is enabledCheck the Checkmk configuration files in /omd/sites/<site>/etc/check_mk/ or access the API through the web interface at /check_mk/api/Affected if REST API endpoint is accessible and enabled on the server
-
Review user role assignments for low-privilege accountsAccess the Checkmk web interface: Setup > Users > Roles, or use the command: ls -la ~/var/check_mk/ (for site-specific user configs)Affected if Users with low-privilege roles (e.g., guest, user) exist in the system and can access the REST API
-
Audit API access logs for privilege escalation attemptsCheck logs in ~/var/log/ for API requests, or query the API audit trail if available via the web interface under Event Console or Audit LogAffected if API requests are being made by users with lower-privilege roles accessing endpoints intended for admin or higher roles
Your environment is affected if the installed Checkmk version is 2.2.0 through 2.4.0 (any patch before 2.4.0p16), the REST API is enabled, and low-privilege users can access it.
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 · scoped2.4.0
Upgrade to Checkmk version 2.4.0p16 or later. Prior to patching, restrict API endpoint exposure via network segmentation and review existing user role assignments.
2.4.0p16
- Backup the current Checkmk installation and configuration before proceeding with the upgrade
- Upgrade Checkmk to version 2.4.0p16 or later following the official upgrade documentation
- Verify the upgrade was successful and test that REST API endpoints properly enforce permission validation
- Confirm that low-privileged users can no longer access unauthorized endpoints or sensitive information
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation3.0 h
- Implementation6.0 h
- Testing5.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,752.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-58121 — 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-2025-58121 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