dbcve.org
Centreon WebApplication · Centreon

CVE-2025-3872

HIGH · 7.2 CVSS v3.1 Published 2025-04-24
Fix available
A fix is available. Upgrade to 22.10.28 / 23.04.25 or later.
See remediation →
78/100
Remediation priority · High
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
Improper Neutralization of Special Elements used in an SQL Command ('SQL Injection') vulnerability in Centreon centreon-web (User configuration form modules) allows SQL Injection. A user with high privileges is able to become administrator by intercepting the contact form request and altering its payload. This issue affects Centreon: from 22.10.0 before 22.10.28, from 23.04.0 before 23.04.25, from 23.10.0 before 23.10.20, from 24.04.0 before 24.04.10, from 24.10.0 before 24.10.4.

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 centreon-web's user configuration form modules allows authenticated high-privilege users to inject malicious SQL commands through the contact form request payload, enabling privilege escalation to administrator level.

MitigationUpgrade Centreon to patched versions (22.10.28, 23.04.25, 23.10.20, 24.04.10, or 24.10.4). As an interim measure, implement strict input validation and parameterized queries on user configuration forms.

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:>= 22.10.0, < 22.10.28>= 23.04.0, < 23.04.25>= 23.10.0, < 23.10.20>= 24.04.0, < 24.04.10>= 24.10.0, < 24.10.4

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

CVSS:3.1/AV:N/AC:L/PR:H/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. Identify installed Centreon Web version
    Run 'rpm -qa | grep centreon-web' or check the version file at /usr/share/centreon/VERSION (file path may vary based on installation). On web interface, check Administration > Extensions > or the footer of any Centreon page for version number.
    Affected if The installed version falls within one of these ranges: 22.10.0 to 22.10.27, 23.04.0 to 23.04.24, 23.10.0 to 23.10.19, 24.04.0 to 24.04.9, or 24.10.0 to 24.10.3.
  2. Verify user configuration form is accessible
    Log in to Centreon web interface and navigate to Configuration > Users > Contacts/Users (or Administration > Users > Add a user depending on version). Confirm the contact/user configuration form loads.
    Affected if The user configuration form module is enabled and accessible in the web interface.
  3. Check for non-administrator high-privilege users
    In Centreon web, go to Administration > ACL > Access Groups or Configuration > Users > Contacts and review user accounts. Look for users with 'reach_api', 'reach_configuration', or admin-level rights who are not assigned the 'admin' contact template.
    Affected if There exist non-admin users with elevated privileges (such as reach_api or reach_configuration enabled) who can access the user configuration form.
  4. Inspect web server access logs for suspicious contact form requests
    Review web server logs (typically /var/log/httpd/access_log or /var/log/nginx/access.log) for POST requests to /centreon/api/ or /centreon/main.php with unusual SQL syntax in the request body, such as UNION SELECT, OR 1=1, or single quotes in contact form parameters.
    Affected if Anomalous SQL-like patterns appear in POST requests targeting user configuration endpoints.

You are affected if your Centreon Web version is within any of the listed vulnerable ranges AND you have high-privilege non-admin users who can access the user configuration form.

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 22.10.28 / 23.04.25 / 23.10.20 or later
Fixed in 22.10.2823.04.2523.10.20
Interim mitigation

Upgrade Centreon to patched versions (22.10.28, 23.04.25, 23.10.20, 24.04.10, or 24.10.4). As an interim measure, implement strict input validation and parameterized queries on user configuration forms.

Recommended fix High confidence

Upgrade to Centreon 22.10.28, 23.04.25, 23.10.20, 24.04.10, or 24.10.4 (whichever corresponds to your current release branch)

  1. 1. Identify the current Centreon Web version by checking the 'Administration > Parameters > About' page or running: cat /usr/share/centreon/www/version.txt
  2. 2. Create a full backup of the Centreon database and configuration files before proceeding with the upgrade
  3. 3. Review the official Centreon upgrade documentation for your current version path: https://docs.centreon.com/docs/upgrade/
  4. 4. Upgrade Centreon to the appropriate fixed version based on your current branch: 22.10.28, 23.04.25, 23.10.20, 24.04.10, or 24.10.4
  5. 5. After upgrade, clear caches and restart Centreon services: systemctl restart centengine centreon-broker httpd2 or systemctl restart centengine centreon-broker apache2
  6. 6. Verify the SQL injection vulnerability is resolved by confirming the fixed version is installed and testing that the user configuration form properly sanitizes inputs
Caveat Standard Centreon upgrade may require downtime and could have configuration migration requirements; review release notes before upgrading

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-3872 — 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-3872 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