CVE-2025-4650: Centreon web · SQL Injection
Affects Centreon webSource CVE Database V5
Not known to be exploited · CVSS 7.2 High.
Data as of 26 Oct 2026, 17:16 UTC
- EPSS
- 0.4% chance of exploitation in 30 days – higher than 34% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:HExploitation evidence
Disclosed: evidence found.
CVE published 22 Aug 2025
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.
What to do
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| Centreon web | Affected
| Fixed in– |
AI-suggested
To mitigate CVE-2025-4650, European organizations should: 1) Immediately upgrade Centreon web to the latest patched versions (24.10.9, 24.04.16, or 23.10.26) as soon as they become available. 2) Restrict high-privilege user access to the Centreon web interface using strict role-based access controls and multi-factor authentication to reduce the risk of privilege misuse. 3) Implement network segmentation and firewall rules to limit access to the Centreon web interface only to trusted administrative networks. 4) Monitor logs for unusual SQL query patterns or unexpected database errors that could indicate attempted exploitation. 5) Conduct regular security audits and penetration testing focused on the Centreon environment to detect potential injection points. 6) Employ Web Application Firewalls (WAFs) with custom rules to detect and block SQL injection attempts targeting the Meta Service indicator page. 7) Educate administrators on the risks of SQL injection and the importance of secure coding and configuration practices. These measures, combined with timely patching, will significantly reduce the risk posed by this vulnerability.
Description
User with high privileges is able to introduce a SQLi using the Meta Service indicator page. Caused by an Improper Neutralization of Special Elements used in an SQL Command.This issue affects web: from 24.10.0 before 24.10.9, from 24.04.0 before 24.04.16, from 23.10.0 before 23.10.26.