CVE-2025-8428
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 · uneditedImproper Neutralization of Input During Web Page Generation (XSS or 'Cross-site Scripting') vulnerability in Centreon Infra Monitoring (HTTP Loader widget modules) allows Stored XSS.This issue affects Infra Monitoring: from 24.10.0 before 24.10.13, from 24.04.0 before 24.04.18, from 23.10.0 before 23.10.28.
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 confidenceStored XSS vulnerability in Centreon Infra Monitoring's HTTP Loader widget modules allows authenticated attackers to inject malicious scripts that persist on the server and execute when other users view affected pages. The vulnerability stems from improper input neutralization in the web page generation process.
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>= 23.10.0, < 23.10.28>= 24.04.0, < 24.04.18>= 24.10.0, < 24.10.13CVSS 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
- Low
- User interaction
- Required
- Scope
- Changed
- Confidentiality
- Low
- Integrity
- Low
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:C/C:L/I:L/A:N
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 checksWork through these to decide whether this CVE applies to you.
-
Identify Centreon Web versionAccess the Centreon administration interface and navigate to Administration > Parameters > About, or check the installed package version using your package manager (e.g., rpm -qa | grep centreon-web or dpkg -l | grep centreon-web).Affected if The installed version falls within these ranges: >= 23.10.0 and < 23.10.28, OR >= 24.04.0 and < 24.04.18, OR >= 24.10.0 and < 24.10.13.
-
Confirm HTTP Loader widget is accessibleLog into Centreon as an authenticated user and navigate to Home > Custom Views > Add a widget. Check if the 'HTTP Loader' widget is listed and available for insertion into dashboards.Affected if The HTTP Loader widget is present and can be added to a custom view by an authenticated user.
-
Verify widget configuration accessAttempt to create or edit an HTTP Loader widget instance by adding it to a custom view and accessing its configuration options. Look for fields that accept user input such as URL, headers, or parameters.Affected if The authenticated user can configure an HTTP Loader widget and provide custom values for its settings.
-
Check for existing injected scriptsIf you have admin access, review custom views and dashboards for any HTTP Loader widgets. Inspect the widget configuration for suspicious patterns in URL, header, or parameter fields that may contain script tags (e.g., <script>, javascript:, onerror=).Affected if Any HTTP Loader widget contains unsanitized user input that could execute as JavaScript when viewed by other users.
You are affected if your Centreon Web version is one of the vulnerable versions listed AND the HTTP Loader widget is accessible to authenticated users in your environment.
Generated from the published advisory. Verify against your own configuration.
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 · scoped23.10.2824.04.1824.10.13
Upgrade Centreon to version 24.10.13, 24.04.18, or 23.10.28 (or later) to patch the vulnerability. Until patched, restrict access to the HTTP Loader widget and implement output encoding on any user-controlled data rendered in the widget.
23.10.28 (for 23.10.x branch), 24.04.18 (for 24.04.x branch), or 24.10.13 (for 24.10.x branch)
- 1. Identify your current Centreon Web version by checking the Centreon administration interface or using: cat /usr/share/centreon/VERSION
- 2. Determine which version branch you are on (23.10.x, 24.04.x, or 24.10.x)
- 3. For Centreon 23.10.x: Upgrade to version 23.10.28 or later
- 4. For Centreon 24.04.x: Upgrade to version 24.04.18 or later
- 5. For Centreon 24.10.x: Upgrade to version 24.10.13 or later
- 6. After upgrade, verify the HTTP Loader widget properly sanitizes input to confirm the vulnerability is remediated
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation3.0 h
- Implementation6.0 h
- Testing4.0 h
- Review / QA2.0 h
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 locallyCheck whether your project pulls in CVE-2025-8428 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2025-8428 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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