dbcve.org
Magicinfo 9 ServerApplication · Samsung

CVE-2026-25200

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
A vulnerability in MagicInfo9 Server allows authorized users to upload HTML files without authentication, leading to Stored XSS, which can result in account takeover 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 prior to 21.1090.1 contain an improper authentication vulnerability allowing authorized users to upload HTML files without proper authentication checks. This enables stored XSS attacks where malicious HTML/JavaScript is persisted on the server and executed when other users view the uploaded content, leading to session hijacking and account takeover.

MitigationUpgrade MagicInfo 9 Server to version 21.1090.1 or later. As an interim control, disable or restrict file upload functionality and implement strict content-type validation for any permitted uploads.

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 if MagicInfo 9 Server is installed
    Check for MagicInfo 9 Server process or service running on the system, or look for MagicInfo installation directories
    Affected if MagicInfo 9 Server is found running or installed on the system
  2. Determine the installed version
    Use the product's version information command, about page, or check version metadata in the installation directory
    Affected if The installed version is lower than 21.1090.1 (e.g., 21.x.x older builds, 20.x.x, or earlier)
  3. Verify file upload functionality is accessible
    Check if the file upload endpoint/module is enabled and accessible on the MagicInfo web interface or API
    Affected if File upload functionality is enabled and exposed without proper authentication enforcement
  4. Inspect upload directory for HTML files
    Examine the server's upload directories for any .html or .htm files that may have been uploaded
    Affected if Unexpected or suspicious HTML files are found in upload directories, indicating potential exploitation

A system is affected if MagicInfo 9 Server is running with a version lower than 21.1090.1 and the file upload feature is 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. As an interim control, disable or restrict file upload functionality and implement strict content-type validation for any permitted uploads.

Recommended fix Moderate confidence

21.1090.1

  1. 1. Identify the current version of MagicINFO 9 Server by accessing the server admin interface or checking system information.
  2. 2. Navigate to the official Samsung security advisory at security.samsungtv.com to obtain the patched version 21.1090.1.
  3. 3. Download the MagicINFO 9 Server version 21.1090.1 or later from Samsung's official download portal.
  4. 4. Create a complete backup of the current MagicINFO 9 Server installation, including configuration files and databases.
  5. 5. Follow Samsung's standard upgrade procedure for MagicINFO 9 Server, typically found in the administration documentation.
  6. 6. After upgrading, verify the server is running version 21.1090.1 or later.
  7. 7. Confirm that the file upload functionality now properly validates and restricts file types, preventing HTML file uploads.
  8. 8. Test that legitimate file uploads (images, videos, documents) still function correctly after the patch.

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
  • Testing3.0 h
  • Review / QA2.0 h
11.0 hours of engineering $1,930
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,088.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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