dbcve.org
Centreon WebApplication · Centreon

CVE-2025-6791

HIGH · 8.8 CVSS v3.1 Published 2025-08-22
Fix available
A fix is available. Upgrade to 23.10.26 / 24.04.16 or later.
See remediation →
94/100
Remediation priority · Urgent
Remotely reachable Zero-click

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
In the monitoring event logs page, it is possible to alter the http request to insert a reflect payload in the DB. Caused by an Improper Neutralization of Special Elements used in an SQL Command ('SQL Injection') vulnerability in Centreon web (Monitoring event logs modules) allows SQL Injection.This issue affects web: 24.10.0, 24.04.0, 23.10.0.

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

SQL injection vulnerability in Centreon web's monitoring event logs module allows attackers to inject malicious SQL payloads via manipulated HTTP requests. The vulnerability stems from improper neutralization of special elements in SQL commands, enabling attackers to execute arbitrary SQL queries against the database.

MitigationApply Centreon security patches for versions 23.10.0, 24.04.0, and 24.10.0. If no patch is available, implement input validation and parameterized queries to neutralize SQL injection vectors in the event logs functionality.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
Centreon WebApplication
Affected:>= 23.10.0, < 23.10.26>= 24.04.0, < 24.04.16>= 24.10.0, < 24.10.9

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
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/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. Determine installed Centreon Web version
    Check the Centreon Web interface version by logging into the admin panel and navigating to Administration > Parameters > About, or by running 'rpm -qa | grep centreon-web' on the server
    Affected if The installed version falls within 23.10.0 to 23.10.25, 24.04.0 to 24.04.15, or 24.10.0 to 24.10.8 (unpatched)
  2. Confirm event logs module is accessible
    Verify that the monitoring event logs functionality is enabled and accessible to the user account in question via the Centreon web interface under Monitoring > Event Logs
    Affected if The event logs module is enabled and accessible to the user
  3. Check web server access logs for anomalous event log requests
    Review web server access logs (typically in /var/log/httpd/ or /var/log/nginx/) for requests to the event logs endpoint that contain SQL operators, quotes, or union statements
    Affected if Log entries show SQL injection patterns in event log parameters

A user is affected if they run an unpatched Centreon Web version within the affected ranges (23.10.x before 23.10.26, 24.04.x before 24.04.16, or 24.10.x before 24.10.9) and have the event logs module accessible.

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
Upgrade available Upgrade to 23.10.26 / 24.04.16 / 24.10.9 or later
Fixed in 23.10.2624.04.1624.10.9
Interim mitigation

Apply Centreon security patches for versions 23.10.0, 24.04.0, and 24.10.0. If no patch is available, implement input validation and parameterized queries to neutralize SQL injection vectors in the event logs functionality.

Recommended fix High confidence

Upgrade to Centreon Web 23.10.26, 24.04.16, or 24.10.9 (or later) depending on your current branch

  1. Identify your current Centreon Web version by checking the Centreon interface (Help > About) or using 'rpm -q centreon-web' command
  2. Based on your current version branch, upgrade to the minimum fixed version: 23.10.26 if on 23.10.x, 24.04.16 if on 24.04.x, or 24.10.9 if on 24.10.x
  3. For Debian/Ubuntu: apt-get update && apt-get install centreon-web or apt-get install centreon-web=24.10.9 (specify your target version)
  4. For RHEL/CentOS: yum update centreon-web or dnf update centreon-web
  5. After upgrade, clear browser cache and verify Centreon interface loads correctly
  6. Test that the Monitoring > Event Logs page functions normally post-upgrade
  7. Review Centreon upgrade documentation for any pre-upgrade steps such as backing up the database

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

Fix this in Centreon Web Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing4.0 h
  • Review / QA2.0 h
15.0 hours of engineering $2,640
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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