Menu

Star on GitHub · 3.2k

CVE-2025-4648

8.4 · HIGH

The content of a SVG file, received as input in Centreon web, was not properly checked.

Published May 13, 2025CWE-434EPSS 0.27%

Overview

CVE-2025-4648 is a high-severity vulnerability. It was published on May 13, 2025 and has a CVSS 3.1 base score of 8.4 (HIGH).

This vulnerability has a CVSS 3.1 base score of 8.4, rated HIGH. It can be exploited remotely over the network. Some level of privileges is required for exploitation.

Technical description

The 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.

Remediation

Check the references section for vendor advisories, patches, and mitigation guidance. If immediate patching is not possible, review the CVSS vector to understand the attack surface and apply compensating controls such as network segmentation or access restrictions.

Frequently asked questions

What is CVE-2025-4648?

CVE-2025-4648 is a high-severity vulnerability. It was published on May 13, 2025 and has a CVSS 3.1 base score of 8.4 (HIGH).

How severe is CVE-2025-4648?

This vulnerability has a CVSS 3.1 base score of 8.4, rated HIGH. It can be exploited remotely over the network. Some level of privileges is required for exploitation.

How do I fix or remediate CVE-2025-4648?

Check the references section for vendor advisories, patches, and mitigation guidance. If immediate patching is not possible, review the CVSS vector to understand the attack surface and apply compensating controls such as network segmentation or access restrictions.

How can CyberStrike help with CVE-2025-4648?

CyberStrike is an open-source, AI-augmented pentesting engine. Rather than flag a version number, it tests whether an issue like CVE-2025-4648 is actually reachable in your own applications and APIs, then verifies each finding before reporting it. That tells you if the weakness is a real, exploitable risk in your environment or a false positive you can safely deprioritize.

Related HIGH CVEs from 2025

View all