Centreon MBI
CVE-2025-8432
HIGH
Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain
-
AccessObtain CentreonBI service account
-
DeliveryEmbed malicious script within BI script
-
ExploitScheduled/triggered script execution
-
ExecutionCode execution in trusted context
-
ImpactPrivilege escalation across scope boundary
Vulnerability Assessment
| Weakness |
CWE
OWASP Top 10:2025
A01:2025 - Broken Access Control
ASVS 5.0
V13 - Configuration Default permission hardening
MITRE ATT&CK
1 technique across 1 tactic: Privilege Escalation The technique list with ATT&CK links and the kill-chain view is part of the Basic plan and up. |
| Exploitation Conditions | Exploitation requires the attacker to already possess or control the CentreonBI user account on the Centreon MBI (Monitoring Business Intelligence) module server - this is the specific prerequisite named in the description. The affected feature is the MBI reporting/script engine, where incorrect default permissions let the CentreonBI account embed scripts within other scripts. Exploitation is further limited by the need for user interaction (UI:R per CVSS) to trigger execution of the tampered script, and it only applies to deployments that have the MBI add-on modules installed (not base Centreon). Limiting factors: high-privilege account control, MBI module deployment, and script execution trigger - all of which constrain this to insider/compromised-service-account abuse rather than opportunistic remote attacks. |
| Impact | This is a CVSS 8.4 (High) flaw whose real-world priority is materially lower than the raw score suggests once all signals are weighed. The CVSS vector (AV:N/AC:L/PR:H/UI:R/S:C/C:H/I:H/A:H) is driven to High primarily by the scope change (S:C) and full C/I/A impact, but it explicitly requires HIGH privileges (PR:H) and user interaction (UI:R) - the attacker must already control the privileged CentreonBI service account on the MBI server, so this is a privilege-escalation/abuse-of-trust issue rather than a pre-auth remote compromise. EPSS corroborates the lower urgency: 0.43% probability at the 35th percentile indicates low near-term exploitation likelihood. The CVE is NOT in CISA KEV and no POC is referenced, so there is no public exploit identified at time of analysis. No SSVC decision data was provided in the input. Note a tension worth flagging: the vendor assigns AV:N, yet the root cause (Incorrect Default Permissions, CWE-276, abused by a local service account embedding scripts within scripts on the MBI server) reads as a local/config-bound condition - verify the true attack vector with Centreon before treating this as remotely reachable. Overall: patch in normal cycle for Centreon MBI operators, but it is not an emergency unless the CentreonBI account is exposed or shared. |
| Exploit ScenarioDerived | An actor who has obtained the privileged CentreonBI service account on the Centreon MBI (Business Intelligence) server leverages incorrect default permissions to embed arbitrary scripts within legitimate reporting scripts. When those scripts are executed (user interaction), the embedded code runs in the trusted BI context, enabling code execution and privilege escalation beyond the account's intended scope. No public exploit code is referenced for this CVE. |
Get an e-mail when this CVE is exploited, patched or re-scored. Free account.
Alert meAnalysisAIv1 – Oct 08, 2026
Incorrect default permissions in the Centreon MBI (Monitoring Business Intelligence) reporting modules let a CentreonBI account embed scripts within other scripts, resulting in high-impact compromise of confidentiality, integrity, and availability across the MBI server (scope-changed). Affected releases are Centreon Infra Monitoring 24.10.0 before 24.10.6, 24.04.0 before 24.04.9, and 23.10.0 before 23.10.15; the CVSS vector (PR:H/UI:R) confirms an authenticated, high-privilege actor plus user interaction, and our assessment (CVSS:3.1/AV:L/AC:L/PR:H/UI:R/S:C/C:H/I:H/A:H, 8.4 High) frames this as insider or compromised-service-account abuse rather than an opportunistic remote attack. There is no public exploit identified at time of analysis, no CISA KEV listing, and the EPSS score is low at 0.43% (35th percentile), so real-world priority is materially lower than the raw 8.4 score suggests.
RemediationAI
Apply the vendor-released patch by upgrading Centreon Infra Monitoring to 24.10.6, 24.04.9, or 23.10.15 (or later within the respective branch), as documented in the Centreon security bulletin https://thewatch.centreon.com/latest-security-bulletins-64/cve-2025-8432-centreon-mbi-high-severity-5180, with release artifacts at https://github.com/centreon/centreon/releases. Until upgrading, restrict how the CentreonBI account can be reached and used: treat any credential or session for that account as sensitive, and review/rotate its credentials if a compromise is suspected - the trade-off is operational overhead and potential report-job reconfiguration. Harden the default permissions on MBI script, template, and report directories so only the CentreonBI runtime (and not interactive users or report authors) can write to them; the trade-off is that legitimate report customization may need a controlled, audited deployment path. If MBI is not in active use, disable or uninstall the MBI add-on modules entirely, which removes the attack surface at the cost of losing BI reporting. Limit network reachability to the MBI server and its reporting interfaces to trusted administrative networks, and enable logging/auditing of changes to MBI scripts to detect the script-within-script tampering pattern, accepting that this is detective rather than preventive control.
Affected ProductsAI
Centreon Infra Monitoring with the MBI (Monitoring Business Intelligence) add-on modules is affected. Fixed-version thresholds define the vulnerable ranges: 24.10.0 up to but not including 24.10.6, 24.04.0 up to but not including 24.04.9, and 23.10.0 up to but not including 23.10.15. Deployments running only the base Centreon platform without the MBI modules installed are out of scope, since the flaw resides in the MBI reporting/script engine and its default permissions rather than in core Centreon. No CPE strings were supplied with this record, so matching should be done against the product/version ranges above; vendor release artifacts are listed at https://github.com/centreon/centreon/releases and the dedicated bulletin is at https://thewatch.centreon.com/latest-security-bulletins-64/cve-2025-8432-centreon-mbi-high-severity-5180.
Affects your stack
Find out whether the stacks and servers you run are on an affected version.
Checking this CVE against your own stacks and servers is part of the Basic plan and up.
Technical ContextAI · show details
Centreon MBI is an add-on business-intelligence/reporting component installed on top of Centreon Infra Monitoring; it runs scheduled report-generation jobs and stored scripts under a dedicated CentreonBI service account on the MBI server. The root cause is CWE-276 (Incorrect Default Permissions): the shipped default filesystem/ownership permissions on MBI script and report artifacts are too permissive, allowing a user controlling the CentreonBI account to write or alter report scripts so that one script embeds another ('Embedding Scripts within Scripts'). That injected inner script then executes with the privileges of the MBI reporting engine, which is why the impact is scope-changed (S:C) with High confidentiality, integrity, and availability effects on the MBI host rather than confined to a single component. The vendor/NVD vector (AV:N) and our independent assessment (AV:L) diverge on the access path, but all signals agree on the prerequisites: control of the CentreonBI account, presence of the MBI add-on modules (base Centreon is not affected), and a user-interaction trigger (UI:R) to run the tampered script. The associated tag 'Privilege Escalation' is consistent with the assessed behavior: an already-privileged service account gains further reach through improperly secured defaults.
Know when Centreon gets its next vulnerability
- Watch products and get an email when something new is published
- Check this CVE against your own stack and servers
- Exploit and PoC references, threat intelligence from 22 sources
No credit card · 7-day full trial
Severity by source
AV:N/AC:L/PR:H/UI:R/S:C/C:H/I:H/A:H
Requires control of the CentreonBI service account on the MBI server (PR:H) and a script execution trigger (UI:R); the default-permissions/local script-embedding nature points to AV:L rather than the vendor's AV:N, with full impact and a scope change.
Primary rating from Vendor (bd4443e6-1eef-43f3-9886-25fc9ceeaae7).
CVSS VectorVendor: bd4443e6-1eef-43f3-9886-25fc9ceeaae7
DescriptionCVE.org
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.
Executive ViewAI
Centreon Infra Monitoring's MBI reporting module has a high-severity incorrect default permissions issue that could allow a privileged CentreonBI account to embed scripts and compromise confidentiality, integrity, and availability of the MBI server. Exploitation requires an authenticated, high-privilege actor plus user interaction, and no public exploit identified at time of analysis, so the pressing business risk is concentrated in reporting administrators and the sensitive data those reports contain. Leadership should prioritize exposure validation, privileged-access reduction, and vendor patch tracking while avoiding broad alarm.
No vendor-released patch identified at time of analysis. Interim mitigations: restrict CentreonBI account permissions and remove unnecessary script-embedding capabilities, enforce least privilege for MBI users, enable detailed audit logging and alerting on script creation and execution, network-segment the MBI server, limit interactive access to trusted administrators, and review default MBI permissions against vendor hardening guidance.
Threat Intelligence Overview
How this decision was reached
The engine reads each signal below and applies a fixed list of rules from top to bottom. The first rule that matches sets the recommended action – like a statement, every line is shown.
What every action level means
SSVC AssessmentENISA
Priority Score
Attack Technique
Privilege escalation occurs when an attacker leverages flaws in access control mechanisms to gain permissions beyond what they were originally granted.
displayServiceStatus.php in Centreon 2.5.1 and Centreon Enterprise Server 2.2 (fixed in Centreon web 2.5.3) allows remot
Multiple SQL injection vulnerabilities in Centreon 2.5.1 and Centreon Enterprise Server 2.2 (fixed in Centreon web 2.5.3
Authenticated OS command injection in Centreon Web (Infra Monitoring) lets a high-privilege user execute arbitrary opera
A SQL injection vulnerability in a MediaWiki script in Centreon before 20.04.14, 20.10.8, and 21.04.2 allows remote unau
Centreon v20.10.18 was discovered to contain a SQL injection vulnerability via the esc_name (Escalation Name) parameter
A SQL injection vulnerability in image generation in Centreon before 20.04.14, 20.10.8, and 21.04.2 allows remote authen
A SQL injection vulnerability in reporting export in Centreon before 20.04.14, 20.10.8, and 21.04.2 allows remote authen
Centreon before 19.04.15 allows remote attackers to execute arbitrary OS commands by placing shell metacharacters in RRD
Centreon 19.10 allows remote authenticated users to execute arbitrary OS commands via shell metacharacters in the server
Centreon 19.04 allows attackers to execute arbitrary OS commands via the Command Line field of main.php?p=60807&type=4 (
minPlayCommand.php in Centreon Web before 2.8.27 allows authenticated attackers to execute arbitrary code via the comman
Centreon 18.x before 18.10.6, 19.x before 19.04.3, and Centreon web before 2.8.29 allows the attacker to execute arbitra
NVD
CVE.org
EPSS
GitHub
Exploit-DB