Cyber Resilience

CVE-2025-66255

Dbbroadcast Mozart Next 3000 Firmware

Public PoC
Published
26 November 2025
Modified
03 December 2025
CVSS Score v4 9.9
Click a component to see what it means
Raw vectorCVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:N/SC:H/SI:N/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X
EPSS Score 0.0037 30th percentile
Risk Priority 46 floored blend · peak EPSS

Summary

CVE-2025-66255 is a critical-severity Insufficient Verification of Data Authenticity (CWE-345) vulnerability in Dbbroadcast Mozart Next 3000 Firmware. Its CVSS base score is 9.9 (Critical).

Operationally, exploitation aligns with the MITRE ATT&CK technique Mark-of-the-Web Bypass (T1553.005); ranked at the 30th percentile by exploit likelihood (below the median); it is not currently listed in the CISA KEV catalog; a public proof-of-concept is referenced.

The strongest mitigations our analysis identified map to SC-23 (Session Authenticity) and SI-3 (Malicious Code Protection) — see the control section below for these in your framework.

Deeper analysis AI-assisted summary

Synthesised by an AI model from the NVD description and linked references — a reading aid, not an authoritative source.

CVE-2025-66255 is an unauthenticated arbitrary file upload vulnerability in the upgrade_contents.php endpoint of DB Electronica Telecomunicazioni S.p.A. Mozart FM Transmitter devices, affecting versions 30, 50, 100, 300, 500, 1000, 2000, 3000, 3500, 6000, and 7000. The endpoint fails to validate file headers, cryptographic signatures, or enforce .tgz format requirements, enabling attackers to upload malicious firmware packages. This missing signature validation leads to firmware injection, with the endpoint also facilitating subsequent arbitrary file uploads and remote code execution. The vulnerability is rated with a CVSS v3.1 base score of 9.8 (AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H) and is associated with CWEs 345 (Insufficient Verification of Data Authenticity) and 434 (Unrestricted Upload of File with Dangerous Type).

Any unauthenticated attacker with network access to the affected device can exploit this vulnerability due to its low attack complexity and lack of privileges required. By sending a crafted request to upgrade_contents.php, the attacker can upload arbitrary files disguised as firmware, bypassing all validation checks. Successful exploitation allows injection of malicious firmware, enabling full remote code execution on the device with high impacts on confidentiality, integrity, and availability.

References for this vulnerability include details published at https://www.abdulmhsblog.com/posts/webfmvulns/, which documents the issue but does not specify vendor-provided patches or mitigation steps in the available information.

OWASP Top 10 for Web (2025)

A06:2025 Insecure DesignA08:2025 Software or Data Integrity Failures

EU & UK References

Vulnerability Data

Unauthenticated Arbitrary File Upload (upgrade_contents.php) in DB Electronica Telecomunicazioni S.p.A. Mozart FM Transmitter versions 30, 50, 100, 300, 500, 1000, 2000, 3000, 3500, 6000, 7000 allows an attacker to perform Missing signature validation allows uploading malicious firmware packages. The firmware…

more

upgrade endpoint in `upgrade_contents.php` accepts arbitrary file uploads without validating file headers, cryptographic signatures, or enforcing .tgz format requirements, allowing malicious firmware injection. This endpoint also subsequently provides ways for arbitrary file uploads and subsequent remote code execution

CWE(s)
CWE-345CWE-434

Related Threats

MITRE ATT&CK Enterprise Techniques

T1553.005 Mark-of-the-Web Bypass Defense Impairment
Adversaries may abuse specific file formats to subvert Mark-of-the-Web (MOTW) controls.
attack.mitre.org →
T1190 Exploit Public-Facing Application Initial Access
Adversaries may attempt to exploit a weakness in an Internet-facing host or system to initially access a network.
attack.mitre.org →
T1195 Supply Chain Compromise Initial Access
Adversaries may manipulate products or product delivery mechanisms prior to receipt by a final consumer for the purpose of data or system compromise.
attack.mitre.org →
T1195.001 Compromise Software Dependencies and Development Tools Initial Access
Adversaries may manipulate software dependencies and development tools prior to receipt by a final consumer for the purpose of data or system compromise.
attack.mitre.org →
T1195.002 Compromise Software Supply Chain Initial Access
Adversaries may manipulate application software prior to receipt by a final consumer for the purpose of data or system compromise.
attack.mitre.org →
T1505 Server Software Component Persistence
Adversaries may abuse legitimate extensible development features of servers to establish persistent access to systems.
attack.mitre.org →
Derived from this CVE’s CWE(s) via the direct CWE→ATT&CK cross-walk.

CVEs Like This One

CVE-2025-63228Same product: Dbbroadcast Mozart Dds Next 100
CVE-2025-66256Same product: Dbbroadcast Mozart Dds Next 100
CVE-2025-63227Same product: Dbbroadcast Mozart Dds Next 100
CVE-2025-66250Same product: Dbbroadcast Mozart Dds Next 100
CVE-2025-66253Same product: Dbbroadcast Mozart Dds Next 100
CVE-2025-66261Same product: Dbbroadcast Mozart Dds Next 100
CVE-2025-66263Same product: Dbbroadcast Mozart Dds Next 100
CVE-2025-66262Same product: Dbbroadcast Mozart Dds Next 100
CVE-2025-66260Same product: Dbbroadcast Mozart Dds Next 100
CVE-2025-66251Same product: Dbbroadcast Mozart Dds Next 100

Affected Assets

dbbroadcast
mozart next 3000 firmware
all versions
dbbroadcast
mozart next 3500 firmware
all versions
dbbroadcast
mozart next 50 firmware
all versions
dbbroadcast
mozart next 500 firmware
all versions
dbbroadcast
mozart next 6000 firmware
all versions
dbbroadcast
mozart next 7000 firmware
all versions
dbbroadcast
mozart next 100 firmware
all versions
dbbroadcast
mozart next 1000 firmware
all versions
dbbroadcast
mozart next 2000 firmware
all versions
dbbroadcast
mozart next 30 firmware
all versions
+12 more product configuration(s) — see NVD for full list

Mitigating Controls

Control response

Prevent
Stop it (NIST 800-53)

—

Detect
Catch it (NIST detect / respond)

—

Harden
Shrink the surface (DISA STIG)
  • 8 hardening rules · 5 OS baselines
Validate
Prove the fix (OWASP ASVS)
  • V3.5.5
  • V5.1.1

Mitigating Controls (NIST 800-53 r5) AI

SC-23 Session Authenticity good match

Explicit requirement to protect session authenticity structurally prevents the weakness for communications.

SI-3 Malicious Code Protection good match

Malicious-code protection at entry points blocks dangerous file types from being accepted and executed.

SI-7 Software, Firmware, and Information Integrity good match

Integrity verification tools detect (but do not stop) the acceptance of data lacking authenticity.

CM-7 Least Functionality partial match

Least functionality restricts the file types and automatic processing capabilities the system will accept.

SC-13 Cryptographic Protection partial match

Cryptographic mechanisms can be used to verify authenticity, thereby preventing acceptance of invalid data.

SC-16 Transmission of Security and Privacy Attributes partial match

Associating security attributes with exchanged information supports verification of authenticity.

Mitigating Controls (NIST CSF 2.0) AI

Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→CSF cross-walk (authority under review) — links open the control.

PR.PS-05 mostly match
prevents

Restricting execution of unauthorized software directly blocks dangerous uploaded files from running.

RC.RP-05 mostly match
degrades

CWE-345 directly impairs RC.RP-05's verification of restored-asset integrity/authenticity, largely defeating the outcome while still leaving other restoration-confirmation steps partially viable.

PR.PS-01 partial match
prevents

Hardened configuration baselines can enforce allowed file types and processing rules.

PR.PS-06 partial match
prevents

Secure development practices include input validation and file-type restrictions that prevent this weakness.

Mitigating Controls (ISO/IEC 27001:2022 Annex A) AI

Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→ISO cross-walk (authority under review) — links open the control.

A.8.29 Security testing in development and acceptance mostly match
finds

Security testing can detect missing or weak data authenticity verification.

A.8.20 Networks security partial match
mitigates

Network controls can enforce authenticated channels, reducing risk of accepting unauthentic data.

A.8.21 Security of network services partial match
mitigates

Secure network services often include authenticity checks for data exchanged over those services.

A.8.24 Use of cryptography partial match
prevents

Cryptographic mechanisms directly verify data origin and integrity, preventing acceptance of unauthentic data.

A.8.25 Secure development life cycle partial match
prevents

Secure SDLC incorporates authenticity verification requirements throughout development.

A.8.26 Application security requirements partial match
prevents

Application security requirements can mandate data authenticity verification mechanisms.

Hardening callouts derived

Configuration rules from DISA STIG baselines that bear on weaknesses of the type cited by this CVE. Each rule is shown with the relationship its mapping actually records, against the CWE it was authored against. Derived via CVE→CWE over `controls_xwalks` (authoritative rows only; rows rated `none` are excluded).

Oracle Linux 8 (2 rules)
  • V-248574 YUM must be configured to prevent the installation of patches, service packs, device drivers, or OL 8 system components that have not been digitally signed using a certificate that is recognized and approved by the organization. prevents CWE-345
  • V-248575 OL 8 must prevent the installation of software, patches, service packs, device drivers, or operating system components of local packages without verification they have been digitally signed using a certificate that is issued by a Certificate Authority (CA) that is recognized and approved by the organization. prevents CWE-345
Oracle Linux 9 (1 rule)
  • V-271525 OL 9 must have GPG signature verification enabled for all software repositories. prevents CWE-345
RHEL 7 (2 rules)
  • V-204447 The Red Hat Enterprise Linux operating system must prevent the installation of software, patches, service packs, device drivers, or operating system components from a repository without verification they have been digitally signed using a certificate that is issued by a Certificate Authority (CA) that is recognized and approved by the organization. prevents CWE-345
  • V-204448 The Red Hat Enterprise Linux operating system must prevent the installation of software, patches, service packs, device drivers, or operating system components of local packages without verification they have been digitally signed using a certificate that is issued by a Certificate Authority (CA) that is recognized and approved by the organization. prevents CWE-345
RHEL 8 (2 rules)
  • V-230264 RHEL 8 must prevent the installation of software, patches, service packs, device drivers, or operating system components from a repository without verification they have been digitally signed using a certificate that is issued by a Certificate Authority (CA) that is recognized and approved by the organization. prevents CWE-345
  • V-230265 RHEL 8 must prevent the installation of software, patches, service packs, device drivers, or operating system components of local packages without verification they have been digitally signed using a certificate that is issued by a Certificate Authority (CA) that is recognized and approved by the organization. prevents CWE-345
RHEL 9 (1 rule)
  • V-257822 RHEL 9 must have GPG signature verification enabled for all software repositories. prevents CWE-345

References