dbcve.org
Incorrect Default PermissionsWeakness · CWE-276

CVE-2025-8432

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

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

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 · moderate confidence

Incorrect default permissions in Centreon MBI (Monitoring Business Intelligence) modules allow the low-privileged CentreonBI user account to write or modify script files on the MBI server, enabling script injection/embedding malicious code into existing scripts. This is a local privilege escalation and code execution vulnerability stemming from overly permissive file permissions on script directories.

MitigationApply vendor patches (24.10.6, 24.04.9, or 23.10.15) to correct default file permissions. As a compensating control, audit and restrict write access to MBI script directories so only authorized users can modify scripts.

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
Required
Scope
Changed
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:H/UI:R/S:C/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. Confirm Centreon MBI installation
    Identify if Centreon MBI (Monitoring Business Intelligence) is installed on the system by checking for Centreon packages or the MBI component.
    Affected if Centreon MBI is installed and the version falls within affected ranges (24.x, 23.x) where default permission flaws exist.
  2. Locate the CentreonBI user account
    Check for the existence of the low-privileged CentreonBI user account on the system using 'id centreonbi' or 'getent passwd centreonbi'.
    Affected if The CentreonBI user account exists on the system.
  3. Identify MBI script directories
    Locate directories containing Centreon MBI script files - typically found within the Centreon MBI installation path under scripts or etl directories.
    Affected if MBI script directories exist on the system.
  4. Check file permissions on MBI script directories
    Use 'ls -ld' or 'namei -l' on the MBI script directories to inspect ownership and permissions, specifically looking for world-writable or group-writable bits.
    Affected if MBI script directories grant write permissions to users other than the intended owner (such as world-write or allowing the CentreonBI user to write).
  5. Verify CentreonBI user write access to scripts
    As the CentreonBI user (or using 'sudo -u centreonbi'), attempt to create or modify a test file in the MBI script directory to confirm write access.
    Affected if The CentreonBI user can write or modify files in MBI script directories, indicating the incorrect default permissions are present.

A system is affected if Centreon MBI is installed, the CentreonBI user exists, and that low-privilege user has write access to MBI script directories due to overly permissive default file permissions.

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.6, 24.04.9, or 23.10.15) to correct default file permissions. As a compensating control, audit and restrict write access to MBI script directories so only authorized users can modify scripts.

Recommended fix High confidence

24.10.6, 24.04.9, or 23.10.15 (depending on your current version branch)

  1. Identify the current Centreon MBI (Infra Monitoring) version using 'centreon -MBI --version' or checking the Centreon web interface
  2. For Centreon 24.10.x branch: upgrade to version 24.10.6 or later
  3. For Centreon 24.04.x branch: upgrade to version 24.04.9 or later
  4. For Centreon 23.10.x branch: upgrade to version 23.10.15 or later
  5. Download the appropriate upgrade package from the Centreon official repository or thewatch.centreon.com
  6. Follow Centreon's standard upgrade procedure for MBI modules (usually via Centreon web interface or command line
  7. Verify the upgrade was successful and the default permissions have been corrected
  8. Confirm the CentreonBI user account permissions are properly restricted
Caveat Standard Centreon upgrade risks apply - ensure backup before upgrading, and test in non-production environment first

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

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing2.0 h
  • Review / QA1.0 h
9.0 hours of engineering $1,600
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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