CVE-2025-54445VulnerabilityPublished 23 Jul 2025

CVE-2025-54445: Samsung Electronics MagicINFO 9 Server · XML External Entity (XXE)

Affects Samsung Electronics MagicINFO 9 ServerSource CVE Database V5

Not known to be exploited · 17% EPSS · CVSS 8.2 High : upgrade to 21.1080.0 soon.

Data as of 25 Oct 2026, 19:02 UTC

CVSS 3.1 base score

8.2High

How severe the flaw is on the 0–10 CVSS scale.

EPSS: 17.7% chance of exploitation in 30 days – higher than 97% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch: Available – fixed in 21.1080.0

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

Attack Vector: Network
Attack Complexity: Low
Privileges Required: None
User Interaction: None
Scope: Unchanged
Confidentiality: High
Integrity: Low
Availability: None

Bold values are the worst case: easiest to exploit or largest impact.

Attack Vector: Network: The vulnerable component is bound to the network stack and the set of possible attackers extends beyond the other options listed, up to and including the entire Internet. Such a vulnerability is often termed 'remotely exploitable' and can be thought of as an attack being exploitable at the protocol level one or more network hops away (e.g., across one or more routers).
Attack Complexity: Low: Specialized access conditions or extenuating circumstances do not exist. An attacker can expect repeatable success against the vulnerable component.
Privileges Required: None: The attacker is unauthorized prior to attack, and therefore does not require any access to settings or files to carry out an attack.
User Interaction: None: The vulnerable system can be exploited without any interaction from any user.
Scope: Unchanged: An exploited vulnerability can only affect resources managed by the same security authority. In this case, the vulnerable component and the impacted component are either the same, or both are managed by the same security authority.
Confidentiality: High: There is total loss of confidentiality, resulting in all resources within the impacted component being divulged to the attacker. Alternatively, access to only some restricted information is obtained, but the disclosed information presents a direct, serious impact.
Integrity: Low: Modification of data is possible, but the attacker does not have control over the consequence of a modification, or the amount of modification is limited. The data modification does not have a direct, serious impact on the impacted component.
Availability: None: There is no impact to availability within the impacted component.

Definitions: FIRST CVSS v3.1 specification.

Exploitation evidence

Disclosed: evidence found.
CVE published 23 Jul 2025
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 2026-10-25.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponised: Public exploit code exists in Metasploit or Exploit-DB, or CISA SSVC reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

What to do

Upgrade Samsung Electronics MagicINFO 9 Server to 21.1080.0.

Affected software

Product	Affected	Fixed in
Samsung Electronics MagicINFO 9 Server	Affected =21.1080.0 <21.1080.0	Fixed in 21.1080.0

AI-suggested

1. Immediate upgrade: Organizations should prioritize upgrading MagicINFO 9 Server to version 21.1080.0 or later once Samsung releases a patch or update addressing this vulnerability. 2. XML parser configuration: Until a patch is available, administrators should review and harden XML parser settings to disable external entity processing if configurable. 3. Network segmentation: Restrict the MagicINFO server’s network access to only necessary resources, blocking outbound requests to sensitive internal systems to limit SSRF impact. 4. Web application firewall (WAF): Deploy or update WAF rules to detect and block malicious XML payloads targeting XXE vulnerabilities. 5. Monitoring and logging: Enhance logging of XML processing errors and outbound requests from the MagicINFO server to detect suspicious activity early. 6. Incident response readiness: Prepare to respond to potential exploitation attempts by establishing alerting mechanisms and validating backups of critical configurations. 7. Vendor engagement: Maintain communication with Samsung for official patches and security advisories and apply them promptly.

Description

Improper Restriction of XML External Entity Reference vulnerability in Samsung Electronics MagicINFO 9 Server allows Server Side Request Forgery.This issue affects MagicINFO 9 Server: less than 21.1080.0.

Impact

For European organizations using Samsung MagicINFO 9 Server, this vulnerability poses a significant risk. The ability to perform SSRF can allow attackers to access internal network resources that are otherwise protected, potentially leading to unauthorized data disclosure or reconnaissance for further attacks. Given that MagicINFO servers often manage critical digital signage infrastructure in retail, transportation, corporate environments, and public spaces, exploitation could lead to leakage of sensitive configuration or operational data. Although the vulnerability does not directly impact availability, the confidentiality breach could facilitate subsequent attacks such as lateral movement or data exfiltration. European organizations with interconnected internal networks or those relying heavily on MagicINFO for customer-facing digital signage may face reputational damage and operational risks if exploited. The lack of authentication requirements and user interaction lowers the barrier for attackers, increasing the urgency of mitigation.

CWE-611Improper Restriction of XML External Entity Reference (opens in a new tab)
Base weaknessOWASP Top 10 A02:2025: Security Misconfiguration (opens in a new tab)
The product processes an XML document that can contain XML entities with URIs that resolve to documents outside of the intended sphere of control, causing the product to embed incorrect documents into its output.
Implementation · System Configuration
Many XML parsers and validators can be configured to disable external entity expansion.
OWASP Cheat Sheets
Deserialization (opens in a new tab)
XML Security (opens in a new tab)
XML External Entity Prevention (opens in a new tab)
OWASP ASVS 4.0.3
V5.5.2 (opens in a new tab)
Attack patterns
Data Serialization External Entities Blowup (opens in a new tab)
From MITRE CWE, MITRE CAPEC and OWASP (Top 10, OpenCRE).

References

security.samsungtv.com/securityUpdates (opens in a new tab)

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 23 Jul 2025, 06:04 UTC

WeaknessesCWE-611

Technical details

References

Community reviews

Related threats