VulnerabilityPublished 27 Oct 2025Updated 30 Oct 2025

CVE-2025-10023: Centreon Infra Monitoring · XSS or 'Cross-site Scripting'

Affects Centreon Infra MonitoringSource CVE Database V5

Not known to be exploited · CVSS 6.2 Medium · fixed in 24.10.9 : update Centreon Infra Monitoring when convenient.

Data as of 26 Oct 2026, 15:59 UTC

CVSS 3.1 base score

6.2Medium

How severe the flaw is on the 0–10 CVSS scale.

EPSS: 0.2% chance of exploitation in 30 days – higher than 10% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch: Available – fixed in 24.10.9, 24.04.16, 23.10.26

CVSS:3.1/AV:N/AC:L/PR:H/UI:R/S:C/C:H/I:N/A:N

Attack Vector: Network
Attack Complexity: Low
Privileges Required: High
User Interaction: Required
Scope: Changed
Confidentiality: High
Integrity: None
Availability: None

Bold values are the worst case: easiest to exploit or largest impact.

Attack Vector: Network: The vulnerable component is bound to the network stack and the set of possible attackers extends beyond the other options listed, up to and including the entire Internet. Such a vulnerability is often termed 'remotely exploitable' and can be thought of as an attack being exploitable at the protocol level one or more network hops away (e.g., across one or more routers).
Attack Complexity: Low: Specialized access conditions or extenuating circumstances do not exist. An attacker can expect repeatable success against the vulnerable component.
Privileges Required: High: The attacker is authorized with (i.e., requires) privileges that provide significant (e.g., administrative) control over the vulnerable component that could affect component-wide settings and files.
User Interaction: Required: Successful exploitation of this vulnerability requires a user to take some action before the vulnerability can be exploited.
Scope: Changed: An exploited vulnerability can affect resources beyond the security scope managed by the security authority of the vulnerable component. In this case, the vulnerable component and the impacted component are different and managed by different security authorities.
Confidentiality: High: There is total loss of confidentiality, resulting in all resources within the impacted component being divulged to the attacker. Alternatively, access to only some restricted information is obtained, but the disclosed information presents a direct, serious impact.
Integrity: None: There is no loss of integrity within the impacted component.
Availability: None: There is no impact to availability within the impacted component.

Definitions: FIRST CVSS v3.1 specification.

Exploitation evidence

Disclosed: evidence found.
CVE published 27 Oct 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.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponised: Public exploit code exists in Metasploit or Exploit-DB, or CISA SSVC or the CVSS exploit maturity reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

What to do

Upgrade centreon/centreon to 24.10.9, 24.04.16 or 23.10.26.

Affected software

Product	Affected	Fixed in
GitHubcentreon/centreon`pkg:github/centreon/centreon`Other threats	Affected =23.10.0 <23.10.26 =24.04.0 <24.04.16 =24.10.0 <24.10.9	Fixed in 23.10.26 24.04.16 24.10.9

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

AI-suggested

1. 2. Restrict elevated privileges to the minimum necessary users and regularly review user roles to limit potential attackers' ability to exploit the vulnerability. 3. Implement strict input validation and output encoding on all user-supplied data within the Centreon application, especially in the Services Meta-services modules. 4. Deploy Content Security Policy (CSP) headers to reduce the impact of XSS by restricting the execution of unauthorized scripts. 5. Monitor logs and user activity for unusual behavior indicative of attempted exploitation, focusing on privileged user actions. 6. Conduct security awareness training for administrators to recognize phishing or social engineering attempts that could lead to privilege escalation or exploitation. 7. Consider network segmentation and isolation of the monitoring infrastructure to limit exposure to external threats. 8. Regularly audit and update the Centreon Infra Monitoring environment and dependencies to maintain security hygiene.

Description

Improper Neutralization of Input During Web Page Generation (XSS or 'Cross-site Scripting') vulnerability in Centreon Infra Monitoring (Services Meta-services modules) allows Stored XSS by users with elevated privileges.This issue affects Infra Monitoring: from 24.10.0 before 24.10.9, from 24.04.0 before 24.04.16, from 23.10.0 before 23.10.26.

Impact

For European organizations, the impact of CVE-2025-10023 can be significant due to the critical role Centreon Infra Monitoring plays in overseeing IT infrastructure and services. Successful exploitation could allow attackers to execute malicious scripts in the context of other users, potentially leading to unauthorized access to sensitive monitoring data, session hijacking, or lateral movement within the network. This could compromise confidentiality of operational data and credentials, undermining trust in monitoring outputs and potentially delaying detection of other security incidents. Although the vulnerability does not directly affect system integrity or availability, the indirect consequences of compromised monitoring data or administrative sessions could disrupt incident response and operational continuity. Organizations with complex IT environments and multiple administrators are particularly at risk. The requirement for elevated privileges limits exposure but also highlights the importance of strict access controls. European critical infrastructure sectors, including energy, telecommunications, and finance, often rely on such monitoring tools, increasing the potential impact. Additionally, regulatory frameworks like GDPR emphasize protecting sensitive data, making exploitation of this vulnerability a compliance concern.

CWE-79Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting') (opens in a new tab)
Base weaknessLikelihood of exploit: HighCWE Top 25 (2025): #1OWASP Top 10 A05:2025: Injection (opens in a new tab)
The product does not neutralize or incorrectly neutralizes user-controllable input before it is placed in output that is used as a web page that is served to other users.
Architecture and Design · Libraries or Frameworks
Use a vetted library or framework that does not allow this weakness to occur or provides constructs that make this weakness easier to avoid.
Implementation · Architecture and Design
Understand the context in which your data will be used and the encoding that will be expected. This is especially important when transmitting data between different components, or when generating outputs that can contain multiple encodings at the same time, such as web pages or multi-part mail messages.
Architecture and Design · Implementation · Attack Surface Reduction
Understand all the potential areas where untrusted inputs can enter your software: parameters or arguments, cookies, anything read from the network, environment variables, reverse DNS lookups, query results, request headers, URL components, e-mail, files, filenames, databases, and any external systems that provide…
OWASP Cheat Sheets
Cross Site Scripting Prevention (opens in a new tab)
DOM based XSS Prevention (opens in a new tab)
Injection Prevention (opens in a new tab)
Abuse Case (opens in a new tab)
Deserialization (opens in a new tab)
OWASP ASVS 4.0.3
V5.3.3 (opens in a new tab)
V1.5.1 (opens in a new tab)
Attack patterns
XSS Using MIME Type Mismatch (opens in a new tab)
DOM-Based XSS (opens in a new tab)
Reflected XSS (opens in a new tab)
Stored XSS (opens in a new tab)
Cross-Site Scripting (XSS) (opens in a new tab)
From MITRE CWE, MITRE CAPEC and OWASP (Top 10, OpenCRE).

References

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 3 Nov 2025, 15:57 UTC

WeaknessesCWE-79

Technical details

References

Community reviews

Related threats