dbcve.org
SQL InjectionWeakness · CWE-89

CVE-2025-3767

HIGH · 7.2 CVSS v3.1 Published 2025-04-22
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
78/100
Remediation priority · High
Remotely reachable Zero-click

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
Improper Neutralization of Special Elements used in an SQL Command ('SQL Injection') vulnerability in Centreon BAM (Boolean KPi Listing modules) allows SQL Injection. This page is only accessible to authenticated users with high privileges. This issue affects Centreon BAM: from 24.10 before 24.10.1, from 24.04 before 24.04.5, from 23.10 before 23.10.10, from 23.04 before 23.04.10.

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

SQL injection vulnerability in Centreon BAM's Boolean KPi Listing modules allows authenticated high-privilege users to inject malicious SQL commands through improper neutralization of special elements in SQL queries.

MitigationApply vendor patches (24.10.1, 24.04.5, 23.10.10, or 23.04.10) to remediate the improper neutralization of special SQL elements.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

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
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 checks

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

  1. Identify Centreon installation and version
    Check the Centreon web interface version by logging in and navigating to Administration > Parameters > About, or check the installed package version via command line (e.g., rpm -q centreon, dpkg -l centreon, or inspecting /usr/share/centreon/VERSION file)
    Affected if The installed Centreon version is lower than 23.04.10, 23.10.10, 24.04.5, or 24.10.1
  2. Verify Centreon BAM module is enabled
    Log into Centreon as an administrator and navigate to Configuration > BAM > Boolean KPi Listing (or check if BAM menu is present in the web interface), or inspect the database for centreon BAM tables
    Affected if The BAM module is installed and accessible in the Centreon web interface
  3. Confirm high-privilege user access to BAM
    Check user permissions in Administration > Users > Access Management > Contacts/Groups, or verify if the authenticated user has BAM privileges (typically admin or BAM manager role)
    Affected if The user account used has high-privilege access to BAM modules (admin or dedicated BAM privileges)
  4. Locate Boolean KPi Listing functionality
    Navigate to Configuration > BAM > Boolean KPi > Listing in the Centreon web interface, or query the database tables related to bam_boolean_kpi
    Affected if The Boolean KPi Listing module is present and accessible, indicating the vulnerable code path exists in the environment

If Centreon BAM is installed with a version below the fixed releases and an authenticated high-privilege user can access the Boolean KPi Listing module, the environment is vulnerable to CVE-2025-3767.

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
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Apply vendor patches (24.10.1, 24.04.5, 23.10.10, or 23.04.10) to remediate the improper neutralization of special SQL elements.

Recommended fix High confidence

24.10.1, 24.04.5, 23.10.10, or 23.04.10 depending on your current branch (24.10, 24.04, 23.10, or 23.04)

  1. 1. Identify the currently installed Centreon BAM version by checking Centreon web interface (About section) or using command line: centreon -v
  2. 2. Based on your current version branch, plan upgrade to the minimum fixed version: for 24.10.x upgrade to 24.10.1, for 24.04.x upgrade to 24.04.5, for 23.10.x upgrade to 23.10.10, for 23.04.x upgrade to 23.04.10
  3. 3. Back up the Centreon database and configuration files before proceeding with upgrade
  4. 4. Follow Centreon official upgrade documentation for your specific version branch (refer to docs.centreon.com)
  5. 5. Apply upgrade via your package manager (apt-get upgrade or yum update depending on OS) or Centreon web upgrade wizard
  6. 6. After upgrade, verify the Centreon BAM module version matches the target fixed release
  7. 7. Test that Centreon BAM functionality works correctly, especially Boolean KPi Listing modules
  8. 8. Verify the SQL injection vulnerability is resolved by confirming the fixed version is running
Caveat Standard Centreon upgrade risks apply - test in staging environment first, ensure plugins and extensions are compatible with target version

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

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation2.0 h
  • Testing3.0 h
  • Review / QA2.0 h
9.0 hours of engineering $1,570
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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