Skip to content
Server Security Center
KEVcritical9.8

CVE-2025-4632: Samsung MagicINFO 9 Server Path Traversal

Samsung MagicINFO 9 Server · listed in the CISA catalog of actively exploited vulnerabilities since 2025-05-22.

CVSS v3.1 (CVE record)
9.8
critical
EPSS (exploit probability, 30 days)
22%
higher than 97.7% of all CVEs
Added to CISA KEV
2025-05-22
US federal due date 2025-06-12
Automatable (CISA SSVC)
yes
technical impact: total

CVE-2025-4632 explained

CVE-2025-4632 is a path traversal vulnerability in Samsung MagicINFO 9 Server versions before 21.1052. It lets attackers write arbitrary files with system authority. CISA lists it as known to be exploited, so unpatched servers face a real and active risk.

Impact

An unauthenticated attacker with network access can write arbitrary files on the server as system authority. No user interaction is needed and attack complexity is low. This can lead to full compromise of confidentiality, integrity and availability. CISA rates the flaw as automatable, meaning it can be exploited at scale, with total technical impact. Attackers are known to use it. Ransomware use is listed as unknown.

Who is affected

The CVE record lists Samsung Electronics MagicINFO 9 Server versions before 21.1052 as affected. Version 21.1052 contains the fix. This version data was published in the CVE record by its CNA (samsung.tv_appliance).

Written with AI from the data on this page and checked against it automatically.

Official description

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

CISA required action: Apply mitigations per vendor instructions, follow applicable BOD 22-01 guidance for cloud services, or discontinue use of the product if mitigations are unavailable.

CISA notes

Affected and fixed versions

From the CVE record published by the vendor or CVE numbering authority.

  • Samsung Electronics MagicINFO 9 Server
    Affected
    • < 21.1052
    Fixed in
    • 21.1052

How to fix it

  • Update to a fixed version: 21.1052.
  • Vendor advisory: security.samsungtv.com/securityUpdates
  • CISA's deadline for US federal agencies: 2025-06-12 (passed) – a useful benchmark for everyone else, too.

What to do

  1. Update all MagicINFO 9 Server installations to version 21.1052 or later.
  2. Follow the Samsung vendor advisory and apply any mitigations it describes.
  3. Restrict network access to the server and keep it off the internet where possible.
  4. Check servers for unexpected or modified files and other signs of compromise, since the flaw is known to be exploited.
  5. If mitigations cannot be applied, discontinue use of the product as CISA's required action states.

Written with AI from the data on this page and checked against it automatically.

CISA's assessment (SSVC)

Exploitation
Exploited in the wild
Automatable
Yes – attackers can automate it at scale
Technical impact
Total – full control of the component or total information disclosure

Weakness: CWE-22 Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal')

Questions about CVE-2025-4632

Is CVE-2025-4632 being exploited?
Yes. CISA added it to its Known Exploited Vulnerabilities catalog on 2025-05-22, with a US federal due date of 2025-06-12. Whether it is used in ransomware campaigns is listed as unknown.
Does an attacker need credentials?
No. The CVSS vector shows network access, no privileges and no user interaction are required, and CISA rates the vulnerability as automatable.
Which version fixes the issue?
The CVE record names MagicINFO 9 Server version 21.1052 as the fixed version. All earlier versions are affected.

Written with AI from the data on this page and checked against it automatically.

References

Data: CISA Known Exploited Vulnerabilities (public domain) · CVE Program records incl. CISA ADP enrichment · OSV.dev (CC BY 4.0) incl. Ubuntu and Debian security data · FIRST EPSS · endoflife.date. Updated automatically – facts last changed 2026-11-21. Always confirm with the vendor's or distribution's advisory before patching.