CVE-2025-54446
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 · uneditedImproper Limitation of a Pathname to a Restricted Directory ('Path Traversal') vulnerability in Samsung Electronics MagicINFO 9 Server allows Upload a Web Shell to a Web Server.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 · moderate confidenceA path traversal vulnerability in Samsung MagicINFO 9 Server (versions below 21.1080.0) allows attackers to bypass directory restrictions when uploading files, enabling deployment of malicious web shells to the web server and achieving remote code execution.
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< 21.1080.0CVSS 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 checksWork through these to decide whether this CVE applies to you.
-
Confirm Samsung MagicINFO 9 Server installationLocate the MagicINFO 9 Server installation on the system. Check for the presence of MagicINFO Server software, typically installed in a directory named 'MagicINFO' or 'Samsung' under Program Files or a custom installation path. Use system inventory tools or check the list of installed programs to verify the product is present.Affected if The product is installed and no version can be determined or the version is below 21.1080.0
-
Identify installed MagicINFO versionAccess the MagicINFO Server administration interface or check the program files for version information. Common locations include the server's about page, a version info file in the installation directory, or the Windows registry under the MagicINFO installation key. Compare the discovered version against the affected range: versions prior to 21.1080.0 are vulnerable.Affected if The installed version is any version prior to 21.1080.0 (for example, 21.1070.0, 21.1000.0, or older releases)
-
Verify file upload functionality is accessibleDetermine if the file upload feature is enabled and exposed. Check the MagicINFO Server configuration or administration panel for the status of upload modules. If the server is accessible over the network, attempt to identify upload endpoints or check if the web interface allows file uploads. Review server access logs for any upload-related requests.Affected if File upload functionality is enabled and the server is network-accessible, combined with a version below 21.1080.0
-
Inspect upload directory configurationExamine the MagicINFO Server configuration files or admin panel settings related to upload directories. Look for the configured upload path and verify whether the server restricts uploads to a specific directory. Check if the upload directory allows execution of uploaded files (for example, if it is within the web root and contains executable file types).Affected if The upload directory is not restricted to non-executable locations, or traversal sequences can be used to escape the intended directory
A system is affected if Samsung MagicINFO 9 Server is installed with a version lower than 21.1080.0 and the file upload functionality is enabled and accessible.
Generated from the published advisory. Verify against your own configuration.
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 · scoped21.1080.0
Upgrade MagicINFO 9 Server to version 21.1080.0 or later. As an interim control, disable or restrict file upload functionality and implement strict validation on all file path parameters to prevent directory traversal.
21.1080.0 or later
- 1. Obtain the MagicINFO 9 Server version 21.1080.0 or later from Samsung's official support channels (support.samsungsv.com or through your Samsung account representative)
- 2. Before upgrading, perform a complete backup of the MagicINFO 9 Server configuration, database, and any custom content
- 3. Review Samsung's official upgrade documentation for MagicINFO 9 Server to understand the upgrade prerequisites and procedures
- 4. Execute the upgrade to version 21.1080.0 or latest stable release following Samsung's documented upgrade path
- 5. After upgrade completion, verify that the web server is functioning correctly and that file upload functionality is working as expected
- 6. Confirm the path traversal vulnerability is remediated by testing that uploaded files are restricted to allowed directories and cannot escape the restricted directory structure
- 7. Review server logs for any suspicious activity that may indicate exploitation attempts prior to patching
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation6.0 h
- Implementation12.0 h
- Testing8.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $8,448.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-54446 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2025-54446 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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