dbcve.org
Centreon WebApplication · Centreon

CVE-2024-53923

HIGH · 7.2 CVSS v3.1 Published 2025-01-23
Fix available
A fix is available. Upgrade to 23.04.24 / 23.10.19 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
An issue was discovered in Centreon Web 24.10.x before 24.10.3, 24.04.x before 24.04.9, 23.10.x before 23.10.19, 23.04.x before 23.04.24. A user with high privileges is able to achieve SQL injection in the form to upload media.

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

A SQL injection vulnerability exists in Centreon Web's media upload functionality. An authenticated user with high privileges (administrator-level) can inject malicious SQL queries through the media upload form due to improper input sanitization.

MitigationUpgrade Centreon Web to one of the patched versions (24.10.3, 24.04.9, 23.10.19, or 23.04.24) to address the SQL injection vulnerability. If immediate patching is not feasible, restrict administrative access and monitor for suspicious SQL patterns in media upload requests.

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.04.0, < 23.04.24>= 23.10.0, < 23.10.19>= 24.04.0, < 24.04.9>= 24.10.0, < 24.10.3

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. Confirm Centreon Web installation
    Check if Centreon Web is running in your environment by identifying the web interface or checking for Centreon-related processes/services.
    Affected if Centreon Web is not installed in your environment.
  2. Identify installed Centreon Web version
    Locate the Centreon Web version by checking the software documentation for version display location (typically available in the web interface footer, about page, or via command line such as 'rpm -q centreon-web' or 'dpkg -l centreon-web' depending on your OS).
    Affected if The installed version falls within any of these ranges: >= 23.04.0 and < 23.04.24; >= 23.10.0 and < 23.10.19; >= 24.04.0 and < 24.04.9; >= 24.10.0 and < 24.10.3.
  3. Verify administrator-level accounts exist
    Check if there are user accounts with administrator-level privileges in Centreon by accessing the Administration > Users > Contacts/Users panel in the web interface or querying the database user tables.
    Affected if There are administrator-level user accounts configured in Centreon.
  4. Confirm media upload feature is accessible
    Verify that the media upload functionality is accessible by checking if authenticated administrators can access the media/file upload section in Centreon (typically found in Administration > Media or similar upload interfaces).
    Affected if The media upload functionality is enabled and accessible to administrator users.
  5. Review logs for suspicious SQL patterns in upload requests
    Examine Centreon logs (application logs and database logs) for unusual SQL syntax or patterns in media upload requests, particularly looking for SQL operators or comments injected into upload parameters.
    Affected if Logs show SQL injection patterns or unexpected SQL syntax in media upload request parameters.

You are affected if Centreon Web is installed with a version in the affected ranges and administrator-level users can access the media upload functionality.

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.04.24 / 23.10.19 / 24.04.9 or later
Fixed in 23.04.2423.10.1924.04.9
Interim mitigation

Upgrade Centreon Web to one of the patched versions (24.10.3, 24.04.9, 23.10.19, or 23.04.24) to address the SQL injection vulnerability. If immediate patching is not feasible, restrict administrative access and monitor for suspicious SQL patterns in media upload requests.

Recommended fix High confidence

Upgrade to Centreon Web 23.04.24, 23.10.19, 24.04.9, or 24.10.3 (or later) depending on your current major version branch

  1. 1. Identify the currently installed Centreon Web version by checking the About page in the Centreon web interface or running: centreon -V
  2. 2. Based on your current version, determine the appropriate upgrade path to a fixed release:
  3. - If on 23.04.x: upgrade to 23.04.24 or later
  4. - If on 23.10.x: upgrade to 23.10.19 or later
  5. - If on 24.04.x: upgrade to 24.04.9 or later
  6. - If on 24.10.x: upgrade to 24.10.3 or later
  7. 3. Before upgrading, backup the Centreon database and configuration files
  8. 4. Follow the official Centreon upgrade documentation for your version branch
Caveat Standard Centreon upgrade may require downtime and compatibility checks with existing modules/plugins; review release notes for migration requirements

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
  • Implementation2.0 h
  • Testing3.0 h
  • Review / QA2.0 h
10.0 hours of engineering $1,770
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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