CVE-2025-12511VulnerabilityPublished 5 Jan 2026Updated 8 Jan 2026

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

Affects Centreon Infra MonitoringSource CVE Database V5

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

Data as of 25 Oct 2026, 19:02 UTC

CVSS 3.1 base score

6.8Medium

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

EPSS: 0.1% chance of exploitation in 30 days – higher than 9% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch: Available – fixed in 25.10.1, 24.10.4, 24.04.8

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

Attack Vector: Network
Attack Complexity: Low
Privileges Required: High
User Interaction: None
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: None: The vulnerable system can be exploited without any interaction from any user.
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 5 Jan 2026
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 2026-10-25.

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 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 Infra Monitoring to 25.10.1, 24.10.4 or 24.04.8.

Affected software

Product	Affected	Fixed in
CentreonInfra Monitoring	Affected >=25.10.0 <25.10.1 >=24.10.0 <24.10.4 >=24.04.0 <24.04.8	Fixed in 25.10.1 24.10.4 24.04.8
GitHubcentreon/centreon`pkg:github/centreon/centreon`Other threats	Affected =25.10.0 =24.10.0 =24.04.0	Fixed in–

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

AI-suggested

If you cannot patch yet, restrict access to the DSM extension configuration modules to only the most trusted administrators and enforce strict role-based access controls to minimize the number of users with elevated privileges. Implement Web Application Firewall (WAF) rules to detect and block suspicious input patterns that could indicate XSS payloads targeting the monitoring interface. Conduct thorough input validation and output encoding in any custom scripts or configurations related to Centreon to reduce injection risks. Regularly audit user privileges and monitor logs for unusual activity indicative of attempted exploitation. Employ multi-factor authentication (MFA) for all administrative accounts to reduce the risk of credential compromise. Finally, educate administrators about the risks of stored XSS and the importance of cautious handling of input fields within the monitoring platform.

Description

Improper Neutralization of Input During Web Page Generation (XSS or 'Cross-site Scripting') vulnerability in Centreon Infra Monitoring (DSM extenstio configuration modules) allows Stored XSS to user with elevated privileges. This issue affects Infra Monitoring: from 25.10.0 before 25.10.1, from 24.10.0 before 24.10.4, from 24.04.0 before 24.04.8.

Impact

For European organizations, the impact of CVE-2025-12511 can be substantial, especially those using Centreon Infra Monitoring for critical infrastructure oversight. Successful exploitation could lead to unauthorized disclosure of sensitive monitoring data, session hijacking, or further privilege escalation within the monitoring environment. This compromises the confidentiality of operational data and could indirectly affect the integrity of monitoring results if attackers leverage stolen credentials to manipulate configurations or alerts. Although availability is not directly impacted, the trustworthiness of the monitoring system could be undermined, affecting incident response and operational continuity. Given the central role of monitoring tools in IT operations, such a breach could facilitate lateral movement to other critical systems. European sectors with stringent regulatory requirements around data protection and operational security, such as finance, healthcare, and energy, would face compliance risks and potential reputational damage. The medium severity rating reflects the requirement for elevated privileges to exploit, but the network accessibility and no need for user interaction increase the risk profile in environments where administrative access controls are weak or compromised.

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 12 Jan 2026, 21:10 UTC

WeaknessesCWE-79

Technical details

References

Community reviews

Related threats