> From https://brixsignage.com/blog/magicinfo-9-cve/ . All Brix pages as markdown: https://brixsignage.com/llms.txt

# MagicInfo 9 CVEs, Builds and End-of-Support Dates

MagicInfo 9 builds, CVEs and end-of-support dates, how to check your server for attack, and how to upgrade.

Comparisons Published October 29, 2026

MagicInfo 9 is Samsung's server software for managing Samsung commercial displays. A CVE is the public ID number for a known security flaw. Two CVEs in MagicInfo 9, CVE-2024-7399 and CVE-2025-4632, let an attacker take over the server with no password. Both are on the US government's list of flaws used in real attacks (the CISA KEV list). Attackers have used them to install botnet malware, remote-access tools and cryptominers on unpatched servers. The fix is a software update; the latest build is 21.1092.3 (23 July 2026).

Samsung stops selling MagicInfo On-Premise on 31 December 2026 and ends all support on 31 December 2029. On-Premise licenses are perpetual, so a server you already run keeps working after those dates. After end of sale you cannot buy new licenses, and after end of support you get no security patches. For what to do instead of MagicInfo, see [Samsung MagicInfo end of life: what to do next](https://brixsignage.com/blog/magicinfo-end-of-life/).

## Version history

MagicInfo Server releases, from Samsung's [release information](https://docs.samsungvx.com/docs/display/MSRI/Release+Information):

| Version | First build | First release | Last build listed |
| --- | --- | --- | --- |
| MagicInfo Premium 4 | 4000.1 | 18 April 2016 | 4101.8 (Premium 4.1, 20 November 2017) |
| MagicInfo 6.0 | 6000.0 | 1 June 2018 |  |
| MagicInfo 7.1 | 7100.2 | 21 August 2019 |  |
| MagicInfo 8 | 20.1000.0 | 21 May 2020 | 20.1040.0 (6 October 2023) |
| MagicInfo 9 | 21.1000.3 | 30 April 2021 | 21.1092.3 (23 July 2026) |

Samsung publishes no separate end-of-support dates for MagicInfo 6, 7 or Premium 4. They are older than MagicInfo 8, which is already out of maintenance, so treat them as unsupported.

MagicInfo 9 builds that matter for security:

| Build | Date | Why it matters |
| --- | --- | --- |
| 21.1050.0 | 24 July 2024 | Fix for CVE-2024-7399; later shown still exploitable |
| 21.1052.0 | 7 May 2025 | Hotfix for CVE-2025-4632. Installs over 21.1050.0 only |
| 21.1070.0 | 22 July 2025 | Multi-factor sign-in becomes mandatory |
| 21.1080.0 | 22 July 2025 | Fixes 18 CVEs (CVE-2025-54438 to 54455). Needs a display firmware update first on this and later builds |
| 21.1090.1 | 14 November 2025 | Fixes CVE-2026-25200, 25201, 25202 |
| 21.1091.1 | 11 February 2026 | Fixes CVE-2026-25203; adds SM32HX-P, SM32HX-L and QB13C models |
| 21.1092.3 | 23 July 2026 | Latest build. Fixes an authentication bypass and remote code execution flaw |

Samsung's own end-of-life page links build 21.1080.0 as the latest, which is out of date. Tenable reports that from February 2026 Samsung makes new MagicInfo 9 builds available only through partners ([Tenable](https://www.tenable.com/security/research/tra-2026-16)); ask your reseller for 21.1092.3 if you cannot download it.

To upgrade from MagicInfo 8 or an older MagicInfo 9 build, update the firmware of every display first, then install the server build. Samsung's release notes require this order from 21.1080.0 on.

## Security history

The US National Vulnerability Database lists 24 CVEs for MagicInfo, all in MagicInfo 9 Server, the first in 2024 ([NVD](https://nvd.nist.gov/vuln/search/results?query=MagicINFO)). None is listed for the display-side player. Scores are Samsung's own.

| CVE | What it is | Fixed in | Score | Exploited |
| --- | --- | --- | --- | --- |
| [CVE-2024-7399](https://nvd.nist.gov/vuln/detail/CVE-2024-7399) | Path traversal: an attacker writes any file with system rights | 21.1050.0 (bypass fixed in 21.1052.0) | 8.8 | Yes. CISA KEV list, added 24 April 2026 |
| [CVE-2025-4632](https://nvd.nist.gov/vuln/detail/CVE-2025-4632) | Path traversal that bypasses the CVE-2024-7399 fix | 21.1052.0 | 9.8 | Yes. CISA KEV list, added 22 May 2025 |
| [CVE-2025-54438](https://nvd.nist.gov/vuln/detail/CVE-2025-54438) to 54455 | 18 flaws: file upload, path traversal, code injection, XXE, sign-in bypass, hard-coded credentials | 21.1080.0 | 7.2 to 9.8 | None reported |
| CVE-2026-25200, 25201, 25202 | Stored script injection, unauthenticated file upload, hard-coded database credentials | 21.1090.1 | 9.8, 8.8, 9.8 | None reported |
| CVE-2026-25203 | Wrong default permissions: local privilege escalation | 21.1091.1 | 7.8 | None reported |

What happened in the wild:

-   **30 April 2025:** a public proof of concept for CVE-2024-7399 is published.
-   **Early May 2025:** Arctic Wolf sees attacks on internet-facing MagicInfo servers ([Arctic Wolf](https://arcticwolf.com/resources/blog/cve-2024-7399/)).
-   **5 May 2025:** SANS reports a Mirai botnet variant uploading a web shell through MagicInfo's update servlet ([SANS ISC](https://isc.sans.edu/diary/31920)).
-   **7 May 2025:** Huntress confirms build 21.1050.0, the official fix, is still exploitable, and advises taking MagicInfo 9 off the internet ([Huntress](https://www.huntress.com/blog/rapid-response-samsung-magicinfo9-server-flaw)). Samsung ships 21.1052.0 the same day.
-   **September 2026:** Huntress reports an intrusion through MagicInfo that installed AnyDesk and a cryptominer, linked to CVE-2025-4632 ([Huntress](https://www.huntress.com/blog/threat-actor-compiles-cryptominer)).

Tenable separately found plaintext credentials in a MagicInfo log file readable by any Windows user, and an unauthenticated upload that can fill the disk, both fixed in 21.1091.1 ([Tenable TRA-2026-16](https://www.tenable.com/security/research/tra-2026-16)).

## Check whether your server was attacked

These signs show up when an attacker has already used CVE-2024-7399 or CVE-2025-4632 against your server.

-   **A service named `PHP5.3.8`.** Check Windows Event Viewer, System log, for Event ID 7045 (a new service installed). Look for ServiceName `PHP5.3.8`, ImagePath `C:\MagicInfo Premium\tomcat\bin\php-cli.exe`, and AccountName `LocalSystem`.
-   **Renamed files in the Tomcat bin folder.** `php-cli.exe` and `php-fpm.exe` under `C:\MagicInfo Premium\tomcat\bin\` are tools renamed to look like PHP, not real PHP binaries. If either file is there and you did not put it there, treat the server as compromised.
-   **Requests to the update servlet.** Search your Tomcat access logs for `/magicinfo/servlet/swupdatefileuploader`. Exploit attempts send requests to this path, so a request from outside your network is a warning sign ([CrowdSec](https://tracker.crowdsec.net/cves/CVE-2024-7399)).
-   **A new `.jsp` file in the Tomcat folders that you did not deploy**, such as `1746466018shell.jsp`. These are web shells an attacker uploads through the update servlet ([SANS ISC](https://isc.sans.edu/diary/31920)).
-   **Unexplained `whoami` or `arp -a` commands**, or any outbound connection from the server to an address you do not recognize.

Found any of these? Take the server off the network, then check it against Huntress' full list of indicators (hashes, download addresses) ([Huntress](https://www.huntress.com/blog/post-exploitation-activities-observed-from-samsung-magicinfo-9-server-flaw)). An update closes the flaw but does not remove anything an attacker already installed: rebuild the server and change every admin password before you reconnect it.

## Upgrade and protect MagicInfo 9

To keep MagicInfo 9 safe until you migrate:

1.  Find your current build, shown at the bottom of the login page and the dashboard. Update every display's firmware first, then the server build, in order, up to 21.1092.3.
2.  If your database is PostgreSQL, MagicInfo 9 needs 15.x: back up your database, install PostgreSQL 15.x, then restore it (21.1092.3 also supports PostgreSQL 18). MagicInfo 9 also runs on SQL Server; 21.1092.3 adds support for SQL Server 2022 and 2025.
3.  Keep the server off the public internet. Displays reach it over your own network or a VPN.
4.  Serve it over HTTPS only, close every port you do not need, and keep multi-factor sign-in on (Samsung's [security recommendations](https://vxt.samsung.com/magic-info-end-of-life)). Block the default ports, TCP 7001 (HTTP) and 7002 (HTTPS), to traffic from outside your network.
5.  Watch Samsung's [security bulletins](https://security.samsungtv.com/securityUpdates) every month. MagicInfo fixes appear there before NVD.

## Regional end-of-sale dates differ

Your region's dates can differ from the global dates above:

-   **Germany:** Samsung's own MagicInfo page gives February 2026 as the last month for new-customer orders, August 2026 for existing-customer orders, and August 2029 for the end of updates and support ([Samsung DE](https://www.samsung.com/de/business/display-solutions/magicinfo/)).
-   **Switzerland:** Signethics, a Samsung reseller, states existing customers can order extra licenses until 31 December 2027 ([Signethics FAQ PDF](https://magicinfosaas.ch/wp-content/uploads/2026/04/FAQ-zu-MagicINFO-End-of-Sales-on-magicinfosaas.ch-EN.pdf)).

Get your own region's dates in writing from your reseller before you plan around the global date.

## Which displays take MagicInfo

-   **2024 models (Tizen 8) still ship the MagicInfo player.** The datasheet for the 115-inch QHFX lists MagicInfo Player S10 alongside VXT ([Samsung datasheet](https://images.samsung.com/is/content/samsung/assets/de/display/pdf/Datenblatt_Smart-Signage_LH115QHFEBGXEN.pdf)).
-   **MagicInfo 9 builds add display models.** Build 21.1091.1 (February 2026) added three.

For which displays run VXT instead, and the migration steps, see [Samsung MagicInfo end of life: what to do next](https://brixsignage.com/blog/magicinfo-end-of-life/).

## VXT plans and terms

Samsung sells VXT, its MagicInfo replacement, on a per-screen plan with single sign-on available from the RM P and P Series plans up. Online purchase is US only, by card; outside the US, Samsung sends buyers to its help desk or a reseller. The X Series plan adds a 24/7 call center and is sold on a sales quote. See Samsung's [S Series](https://vxt.samsung.com/digital-signage-cms/s-series), [P Series](https://vxt.samsung.com/digital-signage-cms/p-series) and [plans](https://vxt.samsung.com/pricing) pages for current pricing.

-   **Trial:** 60 days, no payment details needed.
-   **Hosting:** VXT is Samsung's cloud. There is no on-premise VXT. Samsung publishes no data center regions; its privacy policy says personal data goes to Korea, the US and the UK ([VXT privacy policy](https://vxt.samsung.com/mx/politica-de-privacidad)).
-   **MagicInfo licenses:** Samsung publishes no list price and refers buyers to distributors. An authorized Samsung partner, ScreenCom, lists a MagicInfo Premium on-premise license at a per-player price excluding VAT, with one Maintenance license needed per Premium connection for the MagicInfo 8 to 9 upgrade ([MagicInfo Services](https://www.magicinfoservices.com/product/magicinfo-premium-licenses)).

## Decision tree for large Samsung fleets

Work through these in order. Each answer narrows the path.

1.  **Is any screen on Samsung's own MagicInfo Cloud?** Yes: Samsung ends that service on 28 February 2027. Move it first.
2.  **Is the server on MagicInfo 8 or older?** Yes: upgrade to MagicInfo 9 (one Maintenance key per Premium connection) or migrate, before any other step. Do not wait on an unpatched server.
3.  **Will the fleet grow, or will displays be replaced, after your region's end-of-sale date?** Yes: buy the licenses you need before the cut-off, or plan to run new displays on another platform from that date.
4.  **Can your team keep MagicInfo 9 patched and off the internet to 2029?** No: migrate in 2027, not 2029.
5.  **What share of displays are on VXT's compatible list?** Those can run VXT, or another vendor's Tizen app, on the display. The rest need a player in the HDMI port, whichever platform you choose.
6.  **Do you need single sign-on or an API?** On VXT those need RM P, P Series or X Series; live remote control needs any plan but S Series. Price the whole fleet at that tier.
7.  **Is the MagicInfo database on PostgreSQL?** The VXT CMS Transformer needs PostgreSQL and the Transformer installed on the MagicInfo server's PC, with the server running.
8.  **Pilot before you commit.** Move one site of 10 to 20 screens, run it for two weeks, following [a staged rollout plan](https://brixsignage.com/blog/digital-signage-implementation-plan/), then roll out site by site.

The options themselves (VXT, another CMS with a Tizen app, staying on MagicInfo 9, or an HDMI player) are compared in [Samsung MagicInfo end of life: what to do next](https://brixsignage.com/blog/magicinfo-end-of-life/).

## What to ask Samsung or your reseller

-   What are the end-of-sale, Cloud end-of-service and end-of-support dates for our region? Confirm them in writing.
-   Until what date can we order extra Premium, Lite and RM licenses, and at what price?
-   When does the license activation server stop activating keys, including offline activation?
-   Which build is current, and how do we get it if downloads are partner-only?
-   Do your 2025 and 2026 display models run the MagicInfo player, or VXT only?
-   Which of our display models run VXT on the display, and which features does each support?
-   What is our VXT price per screen at our fleet size, for S, P and X Series?
-   Does the CMS Transformer support our MagicInfo version and database? What does it not migrate (for example video walls, data links, user accounts)?
-   Where is VXT data hosted, and can we choose the region?
-   If a partner hosts our MagicInfo, what is its service end date, in our contract?

See [questions to ask any digital signage vendor](https://brixsignage.com/blog/questions-to-ask-a-digital-signage-vendor/) for more to check before you sign.

## Where Brix fits

Brix is a cloud signage CMS that runs on a player plugged into each display's HDMI port, such as the Amazon Signage Stick ($99.99), so it works the same on every Samsung display, whatever its age or Tizen version. There is no server to patch. It costs $6 per screen per month billed annually, or $8 billed monthly, with single sign-on (OpenID Connect) and every other feature on one plan, and Brix moves your content, playlists and screens for you free, usually in a day. It is not the fit if you want no hardware behind the display: VXT or a CMS with a Tizen app runs on the display itself.

[Talk to us](https://brixsignage.com/demo) about moving a large Samsung fleet off MagicInfo.
