CVE-2025-4648
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 · uneditedThe content of a SVG file, received as input in Centreon web, was not properly checked. Allows Reflected XSS. A user with elevated privileges can inject JS script by altering the content of a SVG media, during the submit request. This issue affects web: from 24.10.0 before 24.10.5, from 24.04.0 before 24.04.11, from 23.10.0 before 23.10.22, from 23.04.0 before 23.04.27, from 22.10.0 before 22.10.29.
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 confidenceThe Centreon web application fails to properly sanitize SVG file content during upload, allowing an authenticated user with elevated privileges to inject malicious JavaScript code into SVG media files. When the SVG is rendered or accessed in the browser, the embedded script executes in the user's context (Reflected XSS).
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>= 22.10.0, < 22.10.29>= 23.04.0, < 23.04.27>= 23.10.0, < 23.10.22>= 24.04.0, < 24.04.11>= 24.10.0, < 24.10.5CVSS 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
- Required
- Scope
- Changed
- Confidentiality
- Low
- Integrity
- Low
- Availability
- Low
CVSS:3.1/AV:N/AC:L/PR:H/UI:R/S:C/C:L/I:L/A:L
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.
-
Check Centreon web versionLog into Centreon and navigate to Administration > Extensions > Manager, or check the about/centreon version page. Alternatively, look for a version file in the Centreon installation directory.Affected if The installed version falls within these ranges: 22.10.0 to <22.10.29, 23.04.0 to <23.04.27, 23.10.0 to <23.10.22, 24.04.0 to <24.04.11, or 24.10.0 to <24.10.5
-
Verify if media/SVG upload is accessibleCheck if the current user has access to the Media/Images upload functionality. In Centreon, this is typically found under Configuration > Monitoring > Image Management or a Media section in the left menu.Affected if You have an authenticated account with elevated privileges (admin, super admin) and can access the media upload feature
-
Identify uploaded SVG filesSearch the Centreon media directory (commonly /usr/share/centreon/www/img/media or similar) for .svg files. Use: find /usr/share/centreon -name "*.svg" 2>/dev/nullAffected if SVG files exist in the Centreon media directories
-
Inspect SVG file contents for script tagsExamine the contents of any found SVG files for suspicious elements: grep -l "<script" /path/to/svg/files/*.svg or visually inspect SVG files for <script>, javascript:, onload, onerror, or other event handler attributes.Affected if Any SVG file contains script tags, javascript: URIs, or event handlers like onload/onerror that could execute arbitrary JavaScript
You are affected if your Centreon web version is within the vulnerable ranges AND you have SVG files uploaded that contain malicious script content, accessible to authenticated privileged users.
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 · scoped22.10.2923.04.2723.10.22
Upgrade Centreon to the patched versions (24.10.5, 24.04.11, 23.10.22, 23.04.27, 22.10.29 or later). Until patched, disable SVG media uploads and implement strict server-side content-type and content validation.
Upgrade to Centreon Web version 22.10.29 (if on 22.10.x), 23.04.27 (if on 23.04.x), 23.10.22 (if on 23.10.x), or 24.04.11 (if on 24.04.x)
- 1. Identify the currently installed Centreon Web version by checking the Centreon about page or using: rpm -qa | grep centreon-web (RPM-based) or dpkg -l | grep centreon (DEB-based)
- 2. Based on your current version line, determine the minimum fixed version needed: for 22.10.x upgrade to 22.10.29; for 23.04.x upgrade to 23.04.27; for 23.10.x upgrade to 23.10.22; for 24.04.x upgrade to 24.04.11
- 3. Backup the Centreon database and configuration files before upgrading
- 4. For RHEL/CentOS systems: run 'yum update centreon-web' or 'dnf update centreon-web'
- 5. For Debian/Ubuntu systems: run 'apt-get update && apt-get install centreon-web'
- 6. After upgrade, clear browser cache and verify the Centreon web interface is functional
- 7. Log in and test that SVG media upload functionality works correctly with properly sanitized files
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation4.0 h
- Implementation8.0 h
- Testing6.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $6,176.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-4648 — 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-4648 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