# CVE-2025-3767: SQL Injection in Centreon BAM boolean KPI listing

> Authenticated high-privilege users can execute arbitrary SQL commands in Centreon BAM Boolean KPI listing, potentially compromising data integrity and confidentiality.

- **Severity:** High 7.2 (`CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 22 Apr 2025
- **Updated:** 22 Apr 2025
- **Also known as:** GHSA-xmr8-xw2g-rqh3

## What is CVE-2025-3767?

CVE-2025-3767 is a high-severity SQL injection vulnerability in Centreon BAM, published on 22 Apr 2025. An attacker needs administrator access to exploit it, with no action from the victim.

### Official description

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.

Weakness: CWE-89 (Improper Neutralization of Special Elements used in an SQL Command)

## Which versions are affected by CVE-2025-3767?


## How do I fix CVE-2025-3767?

No fix has been published for CVE-2025-3767 yet. Limit exposure of the affected software until one is available.

## Is CVE-2025-3767 being exploited?

There is no known exploitation of CVE-2025-3767 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2025-3767 and fix it if it is affected.

What it is: CVE-2025-3767 is a high-severity SQL injection vulnerability in Centreon BAM, published on 22 Apr 2025. An attacker needs administrator access to exploit it, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2025-3767 in the wild and no public exploit code.

Affected product: Centreon BAM. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2025-3767/ (Markdown: https://insights.sbomify.com/CVE-2025-3767/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2025-3767
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2025-3767
- OSV: https://osv.dev/vulnerability/CVE-2025-3767

---
From sbomify Insights: https://insights.sbomify.com/CVE-2025-3767/
Summaries are generated and may contain mistakes; the official description above is the record.