Skip to content
CTI Academy Sponsor CTI Academy
HIGH · CVSS 8.8 CISA Known Exploited Vulnerability

CVE-2024-7399

Samsung MagicINFO 9 Server Path Traversal Vulnerability

Samsung MagicINFO 9 Server

Improper limitation of a pathname to a restricted directory vulnerability in Samsung MagicINFO 9 Server version before 21.1050 allows attackers to write arbitrary file as system authority.

CVSS
8.8
HIGH
EPSS
91.9%
30-day exploitation
Ransomware groups
0
recorded exploiting
Published
12 Aug 2024
CWE-22, CWE-434

Exploitation status

CISA Known Exploited Vulnerabilities

Listed by CISA on 24 April 2026. US federal agencies were required to remediate it by 8 May 2026.

EPSS — exploitation probability

FIRST puts the probability of exploitation activity in the next 30 days at 91.9%, which is higher than 99.8% of all scored vulnerabilities. EPSS is a forecast of activity, not a measure of severity, and it is rescored daily.

CVSS vector

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

Frequently asked questions

Is CVE-2024-7399 being exploited by ransomware groups?

No ransomware group in this database is currently recorded as exploiting CVE-2024-7399.

What does CVE-2024-7399 affect?

CVE-2024-7399 affects Samsung MagicINFO 9 Server. Improper limitation of a pathname to a restricted directory vulnerability in Samsung MagicINFO 9 Server version before 21.1050 allows attackers to write arbitrary file as system authority.

How severe is CVE-2024-7399?

CVE-2024-7399 is rated HIGH with a CVSS base score of 8.8. EPSS puts the probability of exploitation in the next 30 days at 91.9%, higher than 99.8% of all scored vulnerabilities. It is listed in the CISA Known Exploited Vulnerabilities catalog, with a federal remediation deadline of 8 May 2026.

How should organisations respond to CVE-2024-7399?

Apply the vendor patch for Samsung MagicINFO 9 Server as the first priority, and treat any internet-facing instance as the most urgent. Because this vulnerability is associated with ransomware activity, also review whether the affected systems were reachable before patching, rather than assuming that patching alone closes the incident.