CVE-2025-4650
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 · uneditedUser with high privileges is able to introduce a SQLi using the Meta Service indicator page. Caused by an Improper Neutralization of Special Elements used in an SQL Command.This issue affects web: from 24.10.0 before 24.10.9, from 24.04.0 before 24.04.16, from 23.10.0 before 23.10.26.
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 SQL injection vulnerability exists in the Meta Service indicator page where improper neutralization of special elements in SQL commands allows a high-privileged user to inject malicious SQL queries. The vulnerability affects multiple version branches (23.10, 24.04, 24.10) of the web application.
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>= 23.10.0, < 23.10.26>= 24.04.0, < 24.04.16>= 24.10.0, < 24.10.9CVSS 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
- High
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:H/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 installed Centreon web versionLog into the Centreon web interface and navigate to the About page (typically Administration > About) or check the package version on the server using your package manager (e.g., 'rpm -qa | grep centreon-web' or 'dpkg -l | grep centreon-web')Affected if The installed version falls within any of these ranges: >= 23.10.0 and < 23.10.26, OR >= 24.04.0 and < 24.04.16, OR >= 24.10.0 and < 24.10.9
-
Confirm access to Meta Service indicator featureNavigate to the Meta Service indicator page in the Centreon interface (typically under Monitoring > Meta Services or a similar path depending on your version)Affected if The Meta Service indicator page is accessible and functional in your installation
-
Verify high-privilege user accounts existCheck user account roles in Administration > Users > Accessibility options (or Administration > Users > Contacts/Users) to identify accounts with high privileges such as admin, supervisor, or custom roles with extensive accessAffected if There are user accounts with high privileges (admin, super admin, or equivalent) that can access the Meta Service indicator page
You are affected if your Centreon web version is less than 24.10.9, 24.04.16, or 23.10.26 AND the Meta Service indicator page is accessible to high-privileged users in your environment.
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.
From vendor data23.10.2624.04.1624.10.9
Apply the patched versions (24.10.9, 24.04.16, or 23.10.26) to remediate the SQL injection vulnerability. Given the high-privilege requirement, ensure proper access controls and least-privilege principles are enforced even on patched versions.
- Consultation4.0 h
- Implementation8.0 h
- Testing8.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $6,656.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-4650 — 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-4650 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