dbcve.org
Magicinfo 9 ServerApplication · Samsung

CVE-2025-54440

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

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
Unrestricted Upload of File with Dangerous Type vulnerability in Samsung Electronics MagicINFO 9 Server allows Code Injection.This issue affects MagicINFO 9 Server: less than 21.1080.0.

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.1080.0 contain an unrestricted file upload vulnerability that fails to properly validate uploaded file types, allowing attackers to upload files with dangerous extensions (e.g., executable scripts, web shells). This enables remote code injection and potential complete server compromise.

MitigationUpgrade MagicINFO 9 Server to version 21.1080.0 or later. If immediate upgrade is not feasible, restrict or disable the file upload functionality and implement strict file type validation at the application and web server level.

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.1080.0

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
    Locate the version information for your MagicINFO 9 Server installation (check the application admin panel, about page, or installation logs)
    Affected if The installed version is anything prior to 21.1080.0 (for example, 21.1070.0 or older)
  2. Confirm the file upload feature is accessible
    Determine whether the file upload functionality is enabled and exposed on your MagicINFO 9 Server (review the server configuration or admin settings)
    Affected if The file upload feature is enabled and reachable from the network without additional access controls
  3. Review current file type validation configuration
    Inspect the server's upload configuration or application settings to identify what file type restrictions, if any, are currently enforced on uploaded files
    Affected if There are no file type restrictions in place, or only minimal validation that permits executable extensions such as .exe, .php, .jsp, .asp, or .sh
  4. Examine web-accessible directories for suspicious files
    Search the web root and upload directories for unfamiliar script files with extensions like .php, .jsp, .asp, .exe, .phtml, or .sh that were not intentionally uploaded by administrators
    Affected if Unexpected script or executable files are present in directories accessible via HTTP/HTTPS

You are affected if your MagicINFO 9 Server version is below 21.1080.0 AND the file upload feature is enabled without strict file type validation.

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.1080.0 or later
Fixed in 21.1080.0
Vendor patch security.samsungtv.com →
Interim mitigation

Upgrade MagicINFO 9 Server to version 21.1080.0 or later. If immediate upgrade is not feasible, restrict or disable the file upload functionality and implement strict file type validation at the application and web server level.

Recommended fix High confidence

21.1080.0

  1. Backup all MagicINFO 9 Server data and configuration before proceeding with the upgrade
  2. Access the Samsung vendor security portal at https://security.samsungtv.com/securityUpdates to obtain the version 21.1080.0 update
  3. Download the official MagicINFO 9 Server version 21.1080.0 update package from the vendor portal
  4. Follow standard Samsung upgrade procedures for MagicINFO 9 Server to apply the update
  5. Verify that the installed version is 21.1080.0 or later by checking the server administration interface
  6. Confirm the vulnerability is remediated by verifying file upload restrictions are functioning correctly

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

Fix this in Magicinfo 9 Server Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing12.0 h
  • Review / QA4.0 h
28.0 hours of engineering $4,760
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,616.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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