CVE-2025-66256: Critical File Upload in Mozart FM Patch Page

CVE-2025-66256 is a critical (CVSS 9.8) unauthenticated unrestricted file upload in patch_contents.php of the Mozart FM Transmitter web interface. The endpoint has no file type or MIME checks, only a 16MB size limit. The record names no fix, so isolate the management interface and contact the vendor.

What's affected

• Product: Mozart FM Transmitter from DB Electronica Telecomunicazioni S.p.A. (DB Broadcast), web management interface. The record lists models 30, 50, 100, 300, 500, 1000, 2000, 3000, 3500, 6000 and 7000.
• Component: /var/tdf/patch_contents.php, the patch upload page.
• Fixed: neither the record nor the researcher write-up we read names a fixed firmware version or a vendor advisory. Contact the vendor for patch status before assuming one exists.
• Severity: the record scores it 9.8 (critical) with the vector CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H. The record scores this 9.8 (critical). The write-up we read puts it in the High band on its own scale.

How to check if you're exposed

This is a broadcast appliance, so there is no package manager to query. Work from the device and the network.

1. Build a list of every Mozart unit you run, with its model and the web interface version string. The researcher write-up refers to the web management interface version WEBMOZZI-00287.
2. Find out whether the management web interface of each unit is reachable from the internet, from a partner network or from a flat internal network. Check firewall rules and any remote access gateway.
3. Look at the web server logs on a device you can inspect, or at the logs of any proxy in front of it, for requests to the PHP file named in this CVE from addresses you do not recognize.

If the interface is reachable by people outside the small group that needs it, treat the device as exposed.

What to do now

1. Take the management interface off the internet and off any shared network. Put it behind a VPN or a jump host, with an allow list of administrator addresses.
2. Ask DB Broadcast for the patch status of this CVE and for a firmware version that fixes it. Record the answer with your asset notes.
3. If a reverse proxy sits in front of the device, block requests to the PHP pages you do not need until a fix is available.
4. Watch the device for unexpected files, new accounts, changed settings or reboots, and keep a known good copy of its configuration to compare against.
5. Add the rest of your internet facing software to an inventory. Safeguard cannot patch a transmitter, but a free in-browser scan at gold.safeguard.sh/scan and a proper asset inventory help you find the other internet facing software you run, and reachability analysis helps you rank what to fix first.

Why it matters

The weakness is CWE-434, unrestricted upload of a file with a dangerous type. The record says the page has no file type validation and no MIME checking, and the only limit is a 16MB size cap.

This is the second of several upload pages in the same product with the same flaw, which suggests a pattern in how the interface was written and not a single slip. For defenders it means closing one page at a proxy is not enough. Control access to the whole web management interface, and ask the vendor about a complete fix. The record does not mark this as exploited in the wild and it is not on the CISA KEV list. The advisory trail is thin, since the main public source is a researcher write-up rather than a vendor bulletin, so confirm facts with the vendor. Appliances of this kind sit for years without updates, which is why network isolation is the control you can apply today.

Quick check

Sources

• Researcher write-up: 14 vulnerabilities in the Mozart FM Transmitter web interface
• Safeguard Gold entry

Last reviewed: 18 October 2026.