CVE-2025-54455 is a critical (CVSS 9.1) use of hard coded credentials in Samsung MagicINFO 9 Server that allows authentication bypass. It is a separate entry from CVE-2025-54454. Versions below 21.1080.0 are affected; update to 21.1080.0 or later. The sections below cover who is affected, how to check, and what to do first.
What's affected
- MagicINFO 9 Server below 21.1080.0 is affected, per the record.
- Confirm the fixed build in Samsung's bulletin.
- The record text is identical to CVE-2025-54454, so treat the two as a pair.
The record lists CVSS 9.1 (Critical). It is not on the CISA Known Exploited Vulnerabilities list as of the record.
How to check if you're exposed
Read the server version in the admin console and compare it with 21.1080.0. Check whether the console is reachable from untrusted networks, and review sign in logs.
What to do now
- Upgrade to 21.1080.0 or later.
- Restrict console access to management networks.
- Rotate administrative and integration credentials after the upgrade.
- Audit accounts and recent content changes.
- Run the free in browser dependency scan to find affected components across your projects, then check the Gold entry for updates.
Work in that order. Inventory first, because you cannot patch what you do not know you run. Fix the internet facing and shared systems before the internal ones, and write down the version you ended up on so the next review starts from facts rather than memory.
Why it matters
The weakness is CWE-798. Why two entries? The record does not say. They may cover distinct credentials in different components. Samsung's bulletin is the place to check.
Either way, the operational answer is the same: upgrade, restrict access and rotate secrets.
Severity scores are a starting point. The score for this entry is 9.1, and it describes the worst case for the weakness, not your environment. Weigh it against whether the affected component is reachable from outside, who can talk to it, and what it can touch if it is taken over. Reachability analysis helps with that last question for libraries, and the Gold page for this CVE collects the affected versions in one place.
Quick check
Why are there two identical CVEs?
The record does not explain. Both share the same affected range and fix boundary.
Does upgrading alone make me safe?
Upgrade first, then rotate credentials and review for signs of earlier misuse.
Sources
Last reviewed: 18 October 2026.
