Skip to main content
Mallory
CriticalExploited in the wildCISA KEVPublic exploitVulnerability

CVE-2024-7399: Path Traversal Leading to Remote Code Execution in Samsung MagicINFO 9 Server

Published Aug 9, 2024 · Updated 3 days ago
Trending this weekNot trendingOutside this week’s top 100
Mention activity · 30 days2 mentions · peak 1 in a dayToday
CVSS9.8Critical · v3.1
EPSS91.9%100th percentile
CISA KEVYesAdded Apr 24, 2026
In the wildActivePer CISA KEV
Vendor
Samsung Electronics
IdentifiersCVE-2024-7399CWE-22 · Improper Limitation of a Pathname…

CVE-2024-7399 is a path traversal vulnerability in Samsung MagicINFO 9 Server versions before 21.1050. Improper restriction of attacker-controlled pathnames allows arbitrary files to be written outside the intended directory with SYSTEM authority. Attackers can use this capability to upload crafted JSP files and execute arbitrary code on the server. The original fix was incomplete; the related vulnerability CVE-2025-4632 was subsequently addressed in May 2025.

Do you run this?See affected versions in your environment and whether adversaries are exploiting this vulnerability against assets like yours.
Check your exposure
Analyst brief

Impact, mitigation & remediation

What it means and what to do now: patch path, interim mitigations, and the assume-compromise checklist.

Impact

What an attacker gets, and what they’ve been doing with it.

Successful exploitation can compromise the MagicINFO server through arbitrary file writes and SYSTEM-level code execution, allowing modification of application or system files and deployment of malicious server-side code. Exploitation can support malware installation, persistent access, and disruption of the digital-signage management environment. Active exploitation has been observed.

Mitigation

If you can’t patch tonight, do this now.

Restrict access to the MagicINFO server and its administrative interface to trusted IP ranges, and remove unnecessary public internet exposure. Monitor for unexpected server-side file creation and command execution originating from the application service. Access restrictions are compensating controls, not substitutes for applying the complete vendor fixes.

Remediation

Patch, then assume compromise.

Apply current Samsung MagicINFO security updates that address both CVE-2024-7399 and the incomplete-fix vulnerability CVE-2025-4632. Version 21.1050 contained the original August 2024 fix, but that release alone should not be treated as sufficient protection against the related exploitation path. Samsung issued the follow-up fix in May 2025; the exact follow-up fixed version is not available in the supplied information.

Public exploits

Exploits

2 exploits validated by Mallory's analysis.

View more in app →
magicinfo_traversal.rbThis repository contains a single Metasploit module targeting Samsung MagicINFO 9 Server (versions 21.1050.0 and below) for unauthenticated remote code execution (CVE-2024-7399). The exploit leverages a path traversal vulnerability in the SWUpdateFileUploader servlet, allowing an attacker to upload a malicious JSP shell to the server's web directory. The module first checks the target's version by querying /MagicInfo/config.js, then uploads the shell via a crafted POST request to /MagicInfo/servlet/SWUpdateFileUploader with a path traversal in the fileName parameter. Finally, it executes the shell by sending a GET request to the uploaded JSP file. The exploit runs with SYSTEM privileges by default. The code is written in Ruby and is structured as a standard Metasploit exploit module, making it easy to use within the Metasploit framework.Disclosed Apr 30, 2025 · Framework: metasploit · ruby · networkWeaponizedCVE-2024-7399-POCThis repository contains a fully functional exploit for CVE-2024-7399, a remote code execution vulnerability in Samsung MagicInfo's SWUpdateFileUploader endpoint. The main exploit script (CVE-2024-7399.py) is written in Python and orchestrates the attack by uploading malicious JSP payloads (check.jsp and exploit.jsp) to the target server via a path traversal vulnerability in the SWUpdateFileUploader endpoint. The check.jsp payload is used to verify RCE by echoing a random string, while exploit.jsp provides a more advanced webshell that executes arbitrary commands using Java Nashorn scripting. The exploit supports three main modes: RCE verification, arbitrary file upload, and an interactive command shell. The repository also includes a Java command wrapper template for command execution and a requirements.txt for dependencies. The attack vector is network-based, targeting the exposed MagicInfo service, and the endpoints involved are clearly fingerprintable. The exploit is operational, providing a working RCE chain but requiring the attacker to supply commands interactively.davidxbors · Disclosed May 30, 2025 · python · jsp · networkOperational
Exposure surface

Affected products & vendors

Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.

VendorProductType
Samsung ElectronicsMagicinfo 9 Serverapplication
FAQ

Frequently asked questions

Is CVE-2024-7399 exploited in the wild?
Yes. As of Nov 17, 2026, Mallory has reports of exploitation in the wild, and CISA added it to KEV on Apr 24, 2026.
Is there a public exploit for CVE-2024-7399?
Yes. Mallory tracks 2 public exploits or proofs of concept for CVE-2024-7399, the earliest disclosed Apr 30, 2025.
Is there a patch for CVE-2024-7399?
Apply current Samsung MagicINFO security updates that address both CVE-2024-7399 and the incomplete-fix vulnerability CVE-2025-4632. Version 21.1050 contained the original August 2024 fix, but that release alone should not be treated as sufficient protection against the related exploitation path.
What products are affected by CVE-2024-7399?
Samsung Electronics Magicinfo 9 Server.
How severe is CVE-2024-7399?
CVE-2024-7399 has a CVSS v3.1 score of 9.8 (Critical) and an EPSS score of 91.9% (100th percentile) as of Nov 17, 2026.
Activity feed

Recent activity

51 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.

View more in app →
+4 more in the timeline. Sign up to see them
Do you run this?See affected versions in your environment and whether adversaries are exploiting this vulnerability against assets like yours.
Check your exposure
Mallory platform

The version that knows your environment.

This page is what’s public. Mallory adds the parts that aren’t: which of your assets are affected, which adversaries are exploiting it right now, and which detections to deploy tonight.
Exposure mappingQuery your assets running an affected version, and investigate the blast radius.
Threat actor evidenceEvery report linking this CVE to a named adversary.
Associated malware2Malware families linked to this CVE, with evidence and IOCs.
Detection signatures3YARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.
Vendor-by-vendor mappingCross-references every affected SKU, including bundled OEM variants.
Social activity41Community discussion across Reddit, Mastodon, and other social sources.