# CVE-2025-8432: CentreonBI user account on the MBI server can execute commands as root by modifying script runned by the CRON

> A CentreonBI user can escalate privileges to root by modifying a script executed by a CRON job due to incorrect default permissions.

- **Severity:** High 8.4 (`CVSS:3.1/AV:N/AC:L/PR:H/UI:R/S:C/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 27 Oct 2025
- **Updated:** 30 Oct 2025
- **Also known as:** GHSA-qq2g-5gj7-w9xg

## What is CVE-2025-8432?

CVE-2025-8432 is a high-severity vulnerability in Centreon Infra Monitoring, published on 27 Oct 2025. An attacker needs administrator access to exploit it, and only if a user opens a file or follows a link.

### Official description

Incorrect Default Permissions vulnerability in Centreon Infra Monitoring (MBI modules) allows Embedding Scripts within Scripts by CentreonBI user account on the MBI server This issue affects Infra Monitoring: from 24.10.0 before 24.10.6, from 24.04.0 before 24.04.9, from 23.10.0 before 23.10.15.

Weakness: CWE-276 (Incorrect Default Permissions)

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


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

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

## Is CVE-2025-8432 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2025-8432 is a high-severity vulnerability in Centreon Infra Monitoring, published on 27 Oct 2025. An attacker needs administrator access to exploit it, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2025-8432 in the wild and no public exploit code.

Affected product: Centreon Infra Monitoring. 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-8432/ (Markdown: https://insights.sbomify.com/CVE-2025-8432/index.md)
```

## Sources

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

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