dbcve.org
Magicinfo 9 ServerApplication · Samsung

CVE-2025-54445

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
Improper Restriction of XML External Entity Reference vulnerability in Samsung Electronics MagicINFO 9 Server allows Server Side Request Forgery.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

This is an XML External Entity (XXE) injection vulnerability in MagicINFO 9 Server that allows attackers to exploit improper XML parsing to perform Server-Side Request Forgery (SSRF). An unauthenticated attacker can send malicious XML payloads containing external entity references to cause the server to make arbitrary HTTP requests to internal or external resources, potentially accessing sensitive internal services or exfiltrating data.

MitigationUpgrade MagicINFO 9 Server to version 21.1080.0 or later to remediate this vulnerability. If immediate patching is not possible, consider disabling XML parsing or implementing input validation/filtering for XML uploads as a temporary compensating control.

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 MagicINFO 9 Server installation and version
    Locate the MagicINFO 9 Server installation directory and check the version information file, typically found in the server's About or System Information page in the management console, or check the installer/manifest files in the installation directory
    Affected if The installed version is below 21.1080.0 (for example, 21.1070.0, 21.1000.0, etc.)
  2. Locate XML upload or import functionality
    Search the MagicINFO 9 Server web interface and API endpoints for features that accept XML file uploads, XML imports, or XML data submissions. Common paths include /upload, /import, /api/xml, or similar endpoints
    Affected if XML upload or parsing features are accessible and enabled on the server
  3. Verify XML parser configuration
    Check the server configuration files (such as web.config, server.xml, or application configuration) for XML parser settings and whether external entity processing is explicitly disabled
    Affected if The XML parser is configured to allow external entity resolution or no XXE protection is configured
  4. Test for XXE vulnerability response
    If you have authorized testing permissions, send a benign XXE payload (such as a crafted XML with an external entity reference to an internal endpoint) and observe whether the server attempts to resolve the external reference
    Affected if The server processes the XML and attempts to fetch external resources, confirming the XXE vulnerability is present

You are affected if MagicINFO 9 Server version is below 21.1080.0 AND XML upload/parsing functionality is enabled and accessible without proper XXE protection configured.

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 remediate this vulnerability. If immediate patching is not possible, consider disabling XML parsing or implementing input validation/filtering for XML uploads as a temporary compensating control.

Recommended fix High confidence

21.1080.0 or later

  1. 1. Access the Samsung MagicINFO 9 Server administration console
  2. 2. Navigate to the System Settings or Administration section
  3. 3. Locate the Software/Firmware Update or Version Management option
  4. 4. Check for available updates - the system should show version 21.1080.0 or later as the available update
  5. 5. Download and apply the update to version 21.1080.0 or newer
  6. 6. After installation, verify the server version reflects 21.1080.0 or later
  7. 7. Restart the MagicINFO service if required by the update process
  8. 8. Test critical functionality to ensure the update did not break existing operations
Caveat Review Samsung release notes for 21.1080.0 for any configuration or feature changes before upgrading

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
  • Implementation6.0 h
  • Testing8.0 h
  • Review / QA4.0 h
22.0 hours of engineering $3,800
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $6,080.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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