Skip to main content
CVE-2024-45756VulnerabilityPublished

CVE-2024-45756: centreon-open-tickets · n/a

Affects centreon-open-ticketsSource CVE Database V5

0

Not known to be exploited · CVSS 7.2 High · fixed in 24.10.0 : patch centreon-open-tickets soon.

Data as of 26 Oct 2026, 07:57 UTC

CVSS 3.1 base score
7.2High
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.4% chance of exploitation in 30 days – higher than 42% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch
Available – fixed in 24.10.0, 24.04.2, 23.10.1 +2
CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:H

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 25 Nov 2024

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponised: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq 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 2026-10-26.

What to do

Upgrade to a fixed release listed under Affected software.

Affected software

ProductAffectedFixed in
GitHubcentreon/centreon-open-ticketspkg:github/centreon/centreon-open-ticketsOther threatsAffected
  • <24.10.0
  • <24.04.2
  • <23.10.1
  • <23.04.3
  • <22.10.2
Fixed in
  • 24.10.0
  • 24.04.2
  • 23.10.1
  • 23.04.3
  • 22.10.2

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

2) Restrict high-privileged user access strictly on a need-to-know basis and enforce strong authentication mechanisms, including multi-factor authentication for administrative accounts. 3) Conduct thorough input validation and sanitization on all user inputs in ticket creation forms, if custom modifications or interim fixes are possible. 4) Monitor logs for unusual SQL errors or suspicious activities related to ticket creation and database queries. 5) Employ web application firewalls (WAFs) with SQL injection detection rules tailored to Centreon’s ticketing endpoints. 6) Regularly audit user privileges and remove unnecessary high-level permissions. 7) Isolate Centreon management interfaces within secure network segments to limit exposure. 8) Prepare incident response plans specifically addressing potential exploitation of this vulnerability. These steps go beyond generic advice by focusing on access control tightening, monitoring, and network segmentation tailored to the Centreon environment.

Description

An issue was discovered in Centreon centreon-open-tickets 24.10.x before 24.10.0, 24.04.x before 24.04.2, 23.10.x before 23.10.1, 23.04.x before 23.04.3, and 22.10.x before 22.10.2. SQL injection can occur in the form to create a ticket. Exploitation is only accessible to authenticated users with high-privileged access.

References

Community reviews

Loading reviews…