dbcve.org
Magicinfo 9 ServerApplication · Samsung

CVE-2026-25202

CRITICAL · 9.8 CVSS v3.1 Published 2026-02-02
Fix available
A fix is available. Upgrade to 21.1090.1 or later.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable No privileges Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
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.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

MagicINFO 9 Server versions before 21.1090.1 contain hardcoded database credentials embedded in the application code or configuration files. Attackers who discover these credentials can directly authenticate to the underlying database and manipulate data without requiring application-level exploitation.

MitigationUpgrade MagicINFO 9 Server to version 21.1090.1 or later. Conduct a security audit to determine if credentials were exposed or exploited, and rotate all database credentials as a precautionary measure.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
Magicinfo 9 ServerApplication
Affected:< 21.1090.1

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

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

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Identify the installed MagicINFO 9 Server version
    Access the MagicINFO server administration interface or check the version information in the installation directory. Common locations include the about page in the admin panel or a version file in the installation folder.
    Affected if The installed version is any version before 21.1090.1 (e.g., 21.1089, 20.x.x, etc.)
  2. Locate configuration files and application code
    Examine the MagicINFO installation directory for configuration files (such as .xml, .properties, .ini, or config files) and application code where database connection strings may be stored.
    Affected if Hardcoded database credentials (username/password) are found embedded in any configuration file or source code within the MagicINFO installation directory
  3. Search for embedded database credentials
    Use grep or a text search tool to scan configuration files and application directories for patterns matching database passwords, connection strings, or SQL credentials. Look for keywords such as 'password', 'dbpass', 'connectionstring', 'jdbc', or hardcoded strings that resemble credentials.
    Affected if Any plain-text or weakly encoded database credentials are discovered in the application code or configuration files
  4. Verify database accessibility
    Attempt to connect to the underlying database using the discovered credentials from the configuration or code. Check if the database port is exposed and if authentication succeeds with the embedded credentials.
    Affected if The database accepts authentication using credentials found in the application configuration, allowing direct unauthorized access

A system is affected if MagicINFO 9 Server version is below 21.1090.1 AND hardcoded database credentials are present in configuration files or application code, allowing direct database authentication.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Upgrade available Upgrade to 21.1090.1 or later
Fixed in 21.1090.1
Interim mitigation

Upgrade MagicINFO 9 Server to version 21.1090.1 or later. Conduct a security audit to determine if credentials were exposed or exploited, and rotate all database credentials as a precautionary measure.

Recommended fix Moderate confidence

MagicINFO 9 Server version 21.1090.1

  1. 1. Backup the current MagicINFO 9 Server installation and database before proceeding with any upgrade.
  2. 2. Download MagicINFO 9 Server version 21.1090.1 or later from the official Samsung support portal (security.samsungtv.com or Samsung's official download center).
  3. 3. Stop the MagicINFO 9 Server service to ensure no active connections during the upgrade.
  4. 4. Install the updated MagicINFO 9 Server version 21.1090.1, following the standard upgrade installation prompts.
  5. 5. After installation, verify that the hardcoded database credentials have been removed or changed by reviewing the configuration files.
  6. 6. Restart the MagicINFO 9 Server service.
  7. 7. Test the database connection and ensure all functionality is working correctly.
  8. 8. Verify the version number reflects the update (21.1090.1 or later) to confirm the upgrade was successful.
Caveat Review release notes for version 21.1090.1 to check for any breaking changes or required configuration changes before upgrading.

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Magicinfo 9 Server Scoped from the published advisory
  • Consultation6.0 h
  • Implementation12.0 h
  • Testing6.0 h
  • Review / QA4.0 h
28.0 hours of engineering $4,980
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $7,968.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-25202 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-25202 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data