dbcve.org
Magicinfo 9 ServerApplication · Samsung

CVE-2026-25201

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

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
An unauthenticated user can upload arbitrary files to execute remote code, leading to privilege escalation 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 an unauthenticated file upload vulnerability allowing remote attackers to upload arbitrary files to the server and execute them, resulting in privilege escalation to system-level access.

MitigationUpgrade MagicINFO 9 Server to version 21.1090.1 or later to remediate the vulnerability. If immediate patching is not possible, restrict network access to the MagicINFO management interface.

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
Required
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/UI:R/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 if MagicINFO 9 Server is running
    Check running processes or services for 'MagicINFO' or 'Samsung' components. On Windows, use Task Manager or run 'tasklist | findstr -i magic' at command prompt.
    Affected if MagicINFO 9 Server process or service is found running on the system
  2. Determine installed MagicINFO version
    Locate the MagicINFO installation directory (commonly under C:\Program Files\Samsung or C:\Samsung) and check version.txt, or check Windows Registry under HKLM\SOFTWARE\Samsung\MagicINFO for Version key.
    Affected if Installed version is lower than 21.1090.1 or version cannot be determined (treat as vulnerable)
  3. Verify MagicINFO web interface is accessible
    Check if port 80, 443, or 8080 (common MagicINFO ports) are listening locally or externally using 'netstat -an | findstr :80' or 'netstat -an | findstr :443'. Attempt local browser access to http://localhost:<port>/ if service suspected.
    Affected if MagicINFO web interface responds and accepts connections from network addresses
  4. Check for unauthorized uploaded files
    Inspect the MagicINFO upload directories (typically under the web root like /upload or /files folders within the installation directory) for unexpected executable files (.exe, .asp, .jsp, .php, .bat, .ps1).
    Affected if Unexpected executable or script files are found in upload directories that were not intentionally placed there
  5. Review web server access logs
    Examine MagicINFO web server logs (located in /logs folder within MagicINFO installation) for POST requests to upload endpoints from unauthenticated or unexpected IP addresses.
    Affected if Multiple POST requests to upload functionality are logged from IPs that should not have access or are unknown

System is affected if MagicINFO 9 Server is running with a version lower than 21.1090.1 and the web management interface is network-accessible.

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 to remediate the vulnerability. If immediate patching is not possible, restrict network access to the MagicINFO management interface.

Recommended fix High confidence

MagicINFO 9 Server version 21.1090.1

  1. 1. Verify the current MagicINFO 9 Server version by accessing the server administration interface or checking system information.
  2. 2. Download MagicINFO 9 Server version 21.1090.1 or later from the official Samsung support portal (security.samsungtv.com).
  3. 3. Back up the current MagicINFO 9 Server configuration, database, and all uploaded content.
  4. 4. Stop the MagicINFO 9 Server service before applying the update.
  5. 5. Install version 21.1090.1 using the standard Samsung upgrade procedure.
  6. 6. Verify the installation was successful by checking the server version displayed in the admin interface.
  7. 7. Restart the MagicINFO 9 Server service.
  8. 8. Validate that the file upload functionality now properly restricts file types and requires authentication.

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

Fix this in Magicinfo 9 Server Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing4.0 h
  • Review / QA2.0 h
12.0 hours of engineering $2,080
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-25201 — 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-25201 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