CVE-2026-25202VulnerabilityPublished 2 Feb 2026Updated 26 Feb 2026

CVE-2026-25202: Samsung Electronics MagicINFO 9 Server · Use of Hard-coded Credentials

Affects Samsung Electronics MagicINFO 9 ServerSource CVE Database V5

Not known to be exploited · CVSS 9.8 Critical.

Data as of 26 Oct 2026, 06:26 UTC

CVSS 3.1 base score

9.8Critical

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

EPSS: 0.4% chance of exploitation in 30 days – higher than 41% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.

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

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

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: High: There is a total loss of integrity, or a complete loss of protection. For example, the attacker is able to modify any/all files protected by the impacted component. Alternatively, only some files can be modified, but malicious modification would present a direct, serious consequence to the impacted component.
Availability: High: There is total loss of availability, resulting in the attacker being able to fully deny access to resources in the impacted component; this loss is either sustained (while the attacker continues to deliver the attack) or persistent (the condition persists even after the attack has completed). Alternatively, the attacker has the ability to deny some availability, but the loss of availability presents a direct, serious consequence to the impacted component (e.g., the attacker cannot disrupt existing connections, but can prevent new connections; the attacker can repeatedly exploit a vulnerability that, in each instance of a successful attack, leaks a only small amount of memory, but after repeated exploitation causes a service to become completely unavailable).

Definitions: FIRST CVSS v3.1 specification.

Exploitation evidence

Disclosed: evidence found.
CVE published 2 Feb 2026
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-26.

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

Affected software

Product	Affected	Fixed in
Samsung ElectronicsMagicINFO 9 Server	Affected =21.1090.1	Fixed in–

AI-suggested

To mitigate CVE-2026-25202, organizations should take immediate and specific actions beyond generic advice: 1) Monitor Samsung’s official channels closely for the release of a security patch or updated MagicINFO 9 Server version that removes hard-coded credentials and apply it promptly. 2) Until a patch is available, restrict network access to the MagicINFO 9 Server database by implementing strict firewall rules, allowing only trusted management hosts to connect. 3) Employ network segmentation to isolate the MagicINFO 9 Server from general user networks and the internet, minimizing exposure. 4) Conduct thorough audits of MagicINFO 9 Server deployments to identify any instances running affected versions and prioritize remediation. 5) Implement continuous monitoring and alerting for unusual database access patterns or unauthorized login attempts. 6) Consider deploying application-layer firewalls or intrusion detection systems capable of detecting anomalous database queries or connections. 7) Review and improve credential management practices in development and deployment to avoid hard-coded secrets in future software versions. 8) Educate IT and security teams about the risks of hard-coded credentials and the importance of timely patching and network controls. These targeted steps will reduce the risk of exploitation while awaiting official patches.

Description

The database account and password are hardcoded, allowing login with the account to manipulate the database in MagicInfo9 Server.This issue affects MagicINFO 9 Server: less than 21.1090.1.

Impact

The impact of CVE-2026-25202 is severe and multifaceted. Exploitation enables attackers to gain unauthorized access to the MagicINFO 9 Server database, compromising the confidentiality of stored data, including potentially sensitive configuration and operational information. Integrity is at risk because attackers can alter database contents, which may lead to unauthorized changes in digital signage content or system configurations, potentially causing misinformation or reputational damage. Availability can also be affected if attackers disrupt database operations or delete critical data, leading to service outages. Since the vulnerability requires no authentication or user interaction and can be exploited remotely, the attack surface is broad. Organizations relying on MagicINFO 9 Server for managing digital signage in retail, transportation hubs, corporate environments, or public spaces face risks of operational disruption and data breaches. The critical CVSS score reflects the high likelihood of exploitation and the extensive damage potential. Additionally, the presence of hard-coded credentials may facilitate lateral movement within networks if attackers leverage compromised servers as footholds. The absence of known exploits in the wild currently provides a limited window for proactive defense, but the risk of future exploitation remains high.

Summary

CVE-2026-25202 is a critical security vulnerability identified in Samsung Electronics MagicINFO 9 Server, specifically affecting versions earlier than 21.1090.1. The root cause is the presence of hard-coded database credentials within the software, classified under CWE-798 (Use of Hard-coded Credentials). These embedded credentials allow any attacker with network access to the MagicINFO 9 Server to authenticate directly to the database without needing prior authorization or user interaction. Once authenticated, the attacker can manipulate the database fully, potentially altering signage content, extracting sensitive information, or disrupting service availability. The vulnerability has a CVSS 3.1 base score of 9.8, indicating critical severity with network attack vector, no required privileges, and no user interaction. The flaw compromises confidentiality, integrity, and availability simultaneously. Although no public exploits have been reported yet, the simplicity of exploitation and the critical nature of the impact make this vulnerability a high priority for remediation. MagicINFO 9 Server is widely used for digital signage management in enterprises and public venues, making the potential attack surface significant. The lack of available patches at the time of disclosure means organizations must implement interim mitigations to reduce exposure. This vulnerability highlights the dangers of embedding static credentials in software, which can be extracted and abused by attackers to gain unauthorized access and control.

CWE-798Use of Hard-coded Credentials (opens in a new tab)
Base weaknessLikelihood of exploit: HighOWASP Top 10 A07:2025: Authentication Failures (opens in a new tab)
The product contains hard-coded credentials, such as a password or cryptographic key.
Architecture and Design
For outbound authentication: store passwords, keys, and other credentials outside of the code in a strongly-protected, encrypted configuration file or database that is protected from access by all outsiders, including other local users on the same system. Properly protect the key (CWE-320).
Architecture and Design
For inbound authentication: Rather than hard-code a default username and password, key, or other authentication credentials for first time logins, utilize a "first login" mode that requires the user to enter a unique strong password or key.
Architecture and Design
If the product must contain hard-coded credentials or they cannot be removed, perform access control checks and limit which entities can access the feature that requires the hard-coded credentials. For example, a feature might only be enabled through the system console instead of through a network connection.
OWASP Cheat Sheets
Key Management (opens in a new tab)
REST Security (opens in a new tab)
JSON Web Token for Java (opens in a new tab)
OWASP Authentication (opens in a new tab)
OWASP ASVS 4.0.3
V2.10.4 (opens in a new tab)
V6.4.1 (opens in a new tab)
V3.5.2 (opens in a new tab)
Attack patterns
Read Sensitive Constants Within an Executable (opens in a new tab)
Try Common or Default Usernames and Passwords (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 27 Feb 2026, 08:09 UTC

WeaknessesCWE-798

Technical details

References

Community reviews

Related threats