Centreon Infra Monitoring up to 23.10.14/24.04.8/24.10.5 MBI Module default permission
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 6.2 | $0-$5k | 0.00 |
Summary
A vulnerability has been found in Centreon Infra Monitoring up to 23.10.14/24.04.8/24.10.5 and classified as critical. Affected is an unknown function of the component MBI Module. This manipulation causes default permission. The identification of this vulnerability is CVE-2025-8432. It is possible to initiate the attack remotely. There is no exploit available. The affected component should be upgraded.
Details
A vulnerability was found in Centreon Infra Monitoring up to 23.10.14/24.04.8/24.10.5. It has been declared as critical. Affected by this vulnerability is an unknown part of the component MBI Module. The manipulation with an unknown input leads to a default permission vulnerability. The CWE definition for the vulnerability is CWE-276. During installation, installed file permissions are set to allow anyone to modify those files. As an impact it is known to affect confidentiality, integrity, and availability. The summary by CVE is:
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.
The weakness was shared by Stago. The advisory is shared at github.com. This vulnerability is known as CVE-2025-8432 since 07/31/2025. The exploitation appears to be easy. The attack can be launched remotely. Additional levels of successful authentication are needed for exploitation. It demands that the victim is doing some kind of user interaction. Neither technical details nor an exploit are publicly available. MITRE ATT&CK project uses the attack technique T1222 for this issue.
Upgrading to version 23.10.15, 24.04.9 or 24.10.6 eliminates this vulnerability.
If you want to get the best quality for vulnerability data then you always have to consider VulDB.
Product
Vendor
Name
Version
- 23.10.0
- 23.10.1
- 23.10.2
- 23.10.3
- 23.10.4
- 23.10.5
- 23.10.6
- 23.10.7
- 23.10.8
- 23.10.9
- 23.10.10
- 23.10.11
- 23.10.12
- 23.10.13
- 23.10.14
- 24.04.0
- 24.04.1
- 24.04.2
- 24.04.3
- 24.04.4
- 24.04.5
- 24.04.6
- 24.04.7
- 24.04.8
- 24.10.0
- 24.10.1
- 24.10.2
- 24.10.3
- 24.10.4
- 24.10.5
License
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔒VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 6.3VulDB Meta Temp Score: 6.2
VulDB Base Score: 4.3
VulDB Temp Score: 4.1
VulDB Vector: 🔒
VulDB Reliability: 🔍
CNA Base Score: 8.4
CNA Vector (Centreon): 🔒
CVSSv2
| AV | AC | Au | C | I | A |
|---|---|---|---|---|---|
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| Vector | Complexity | Authentication | Confidentiality | Integrity | Availability |
|---|---|---|---|---|---|
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
VulDB Base Score: 🔒
VulDB Temp Score: 🔒
VulDB Reliability: 🔍
Exploiting
Class: Default permissionCWE: CWE-276 / CWE-266
CAPEC: 🔒
ATT&CK: 🔒
Physical: No
Local: No
Remote: Yes
Availability: 🔒
Status: Not defined
EPSS Score: 🔒
EPSS Percentile: 🔒
Price Prediction: 🔍
Current Price Estimation: 🔒
| 0-Day | Unlock | Unlock | Unlock | Unlock |
|---|---|---|---|---|
| Today | Unlock | Unlock | Unlock | Unlock |
Threat Intelligence
Interest: 🔍Active Actors: 🔍
Active APT Groups: 🔍
Countermeasures
Recommended: UpgradeStatus: 🔍
0-Day Time: 🔒
Upgrade: Infra Monitoring 23.10.15/24.04.9/24.10.6
Timeline
07/31/2025 CVE reserved10/27/2025 Advisory disclosed
10/27/2025 VulDB entry created
10/27/2025 VulDB entry last update
Sources
Advisory: github.comResearcher: Stago
Status: Confirmed
CVE: CVE-2025-8432 (🔒)
GCVE (CVE): GCVE-0-2025-8432
GCVE (VulDB): GCVE-100-330109
Entry
Created: 10/27/2025 11:32Changes: 10/27/2025 11:32 (65)
Complete: 🔍
Cache ID: 216::103
If you want to get the best quality for vulnerability data then you always have to consider VulDB.
No comments yet. Languages: en.
Please log in to comment.