dbcve.org
Magicinfo 9 ServerApplication · Samsung

CVE-2025-54448

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

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

An unrestricted file upload vulnerability in Samsung MagicINFO 9 Server versions before 21.1080.0 allows attackers to upload dangerous file types, enabling code injection. The lack of proper validation on uploaded files permits execution of malicious code on the affected server.

MitigationUpgrade MagicINFO 9 Server to version 21.1080.0 or later to implement proper file type restrictions and prevent code injection attacks.

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. Confirm MagicINFO 9 Server is installed
    Locate the MagicINFO 9 Server installation on the system. This is typically a Windows server application. Check for the service named 'MagicINFO Server' or look for the installation directory (commonly in C:\Program Files\Samsung or C:\MagicINFO).
    Affected if MagicINFO 9 Server is found on the system
  2. Identify the installed version
    Access the MagicINFO Server management console or check the version information in the installation directory. The version is usually displayed in the admin UI or can be found in a version file within the program directory.
    Affected if The installed version is lower than 21.1080.0
  3. Verify the file upload feature is enabled
    Log into the MagicINFO Server admin interface and navigate to the content management or file upload section. Confirm that the upload functionality is accessible to users.
    Affected if The file upload feature is accessible and operational
  4. Check for upload restrictions on file types
    In the upload configuration settings, examine what file types are allowed. Attempt to identify if there are any restrictions on executable file types (such as .asp, .jsp, .php, .exe, .bat, .sh).
    Affected if No file type restrictions are configured or executable file types are permitted for upload
  5. Review uploaded file storage location
    Check the web server configuration and upload directory to determine if uploaded files are stored in a web-accessible location. Verify if files can be accessed via HTTP/HTTPS.
    Affected if Uploaded files are stored in a web-accessible directory and can be executed via HTTP requests

The environment is affected if MagicINFO 9 Server is installed with a version lower than 21.1080.0 and the file upload feature is accessible without proper 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
Interim mitigation

Upgrade MagicINFO 9 Server to version 21.1080.0 or later to implement proper file type restrictions and prevent code injection attacks.

Recommended fix High confidence

MagicINFO 9 Server 21.1080.0 or later

  1. 1. Check current MagicINFO 9 Server version via the admin console or system information panel
  2. 2. Create a complete backup of the MagicINFO 9 Server database and configuration files
  3. 3. Download MagicINFO 9 Server version 21.1080.0 or later from the official Samsung support portal (security.samsungtv.com or Samsung Business support)
  4. 4. Stop the MagicINFO 9 Server services before applying the update
  5. 5. Apply the upgrade following Samsung's official upgrade documentation for MagicINFO 9 Server
  6. 6. Verify the upgrade was successful by checking the version number in the admin console
  7. 7. Restart MagicINFO services and confirm normal operation
  8. 8. Test that file upload functionality works correctly with proper file type restrictions

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
  • Implementation2.0 h
  • Testing8.0 h
  • Review / QA4.0 h
18.0 hours of engineering $3,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 $4,928.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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