CVE-2026-2751
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 · uneditedBlind SQL Injection via unsanitized array keys in Service Dependencies deletion. Vulnerability in Centreon Centreon Web on Central Server on Linux (Service Dependencies modules) allows Blind SQL Injection.This issue affects Centreon Web on Central Server before 25.10.8, 24.10.20, 24.04.24.
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 confidenceA blind SQL injection vulnerability exists in Centreon Web's Service Dependencies deletion functionality on the Central Server. The vulnerability stems from unsanitized array keys being used directly in SQL queries, allowing authenticated attackers to inject malicious SQL code. This is a critical severity (CVSS 9.8) issue affecting Centreon Web versions prior to 25.10.8, 24.10.20, and 24.04.24.
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>= 24.04.0, < 24.04.24.>= 24.10.0, < 24.10.20>= 25.10.0, < 25.10.8CVSS 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
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
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 Centreon Web versionLocate the Centreon Web installation and retrieve its version number. Common methods include checking the web interface 'About' page, running package queries (rpm -q or dpkg -l), or inspecting version files in the Centreon installation directory.Affected if The installed version falls within any of these ranges: >= 24.04.0 and < 24.04.24; >= 24.10.0 and < 24.10.20; >= 25.10.0 and < 25.10.8
-
Confirm Service Dependencies feature is accessibleDetermine whether the Service Dependencies management functionality is enabled and accessible within the Centreon web interface. This typically involves navigating to the Configuration > Dependencies or similar menu path where service dependency deletion operations can be performed.Affected if The Service Dependencies deletion interface is available to your user account without additional configuration restrictions.
-
Verify authentication and access controlsReview user accounts and profiles that have access to the Service Dependencies management area. Check whether untrusted or low-privilege users can access the deletion functionality.Affected if Users beyond trusted administrators have access to the Service Dependencies deletion feature, as exploitation requires authenticated access to this functionality.
You are affected if your Centreon Web version is below 24.04.24, 24.10.20, or 25.10.8 AND untrusted users can access the Service Dependencies deletion interface.
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 · scoped24.04.24.24.10.2025.10.8
Upgrade Centreon Web to version 25.10.8, 24.10.20, or 24.04.24 or later. Until patches are applied, restrict access to the Service Dependencies management interface to trusted users only.
Upgrade to Centreon Web 24.04.24, 24.10.20, or 25.10.8 (whichever corresponds to your current branch)
- 1. Back up the Centreon database and configuration files before proceeding with the upgrade.
- 2. Review the official Centreon upgrade documentation for your current version: https://documentation.centreon.com/docs/centreon/en/latest/upgrade.html
- 3. Download the appropriate fixed version based on your current installation:
- - For 24.04.x branch: upgrade to 24.04.24
- - For 24.10.x branch: upgrade to 24.10.20
- - For 25.10.x branch: upgrade to 25.10.8
- 4. Stop the Centreon services (centengine, centreon-broker, httpd) before upgrading.
- 5. Follow the standard Centreon upgrade procedure for your Linux distribution.
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation4.0 h
- Implementation8.0 h
- Testing4.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 $5,120.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-2751 — 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-2026-2751 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