dbcve.org
Mozart Next 100 FirmwareOperating system · Dbbroadcast

CVE-2025-66250

CRITICAL · 9.8 CVSS v3.1 Published 2025-11-26
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
100/100
Remediation priority · Urgent
Public exploit 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
Unauthenticated Arbitrary File Upload (status_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 Allows unauthenticated arbitrary file upload via /var/tdf/status_contents.php.

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

Unauthenticated arbitrary file upload vulnerability in the status_contents.php component of DB Electronica Mozart FM Transmitter allows remote attackers to upload arbitrary files without authentication. This critical flaw (CVSS 9.8) affects multiple transmitter models (versions 30 through 7000) and can be exploited to achieve remote code execution.

MitigationApply vendor-provided firmware patches immediately to address the arbitrary file upload vulnerability. If no patch exists, implement network segmentation and restrict access to the vulnerable endpoint via firewall rules or disable the affected PHP component until a fix is available.

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
Mozart Next 100 FirmwareOperating system
Affected:all versions
Mozart Next 1000 FirmwareOperating system
Affected:all versions
Mozart Next 2000 FirmwareOperating system
Affected:all versions
Mozart Next 30 FirmwareOperating system
Affected:all versions
Mozart Next 300 FirmwareOperating system
Affected:all versions
Mozart Next 3000 FirmwareOperating system
Affected:all versions
Mozart Next 3500 FirmwareOperating system
Affected:all versions
Mozart Next 50 FirmwareOperating system
Affected:all versions

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 the device model
    Access the device web interface or check the device label/firmware to confirm it is a Dbbroadcast Mozart Next series device (30, 50, 100, 300, 1000, 2000, 3000, or 3500)
    Affected if The device is any Dbbroadcast Mozart Next model listed in the affected products
  2. Check for status_contents.php endpoint
    Attempt to access the status_contents.php file via HTTP or HTTPS on the device web server (for example: http://[device-ip]/status_contents.php)
    Affected if The endpoint returns a response rather than a 404 error, indicating the file exists on the system
  3. Verify if endpoint allows unauthenticated access
    Access the status_contents.php endpoint without providing any login credentials or session cookie
    Affected if The endpoint loads or accepts requests without requiring authentication
  4. Test for unrestricted file upload
    Submit a test POST request to status_contents.php with a simple file (such as a text file) to see if the upload succeeds without authentication
    Affected if The file upload completes successfully and the file is stored on the system without authentication
  5. Inspect web directory for unexpected files
    If accessible, enumerate the web server document root or upload directories and look for unfamiliar files, especially .php, .js, or .html files that were not intentionally deployed
    Affected if Unexpected files are present in the web directories

If the device is a Dbbroadcast Mozart Next series and the status_contents.php endpoint is accessible without authentication, the environment is affected by this vulnerability.

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.

From vendor data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Apply vendor-provided firmware patches immediately to address the arbitrary file upload vulnerability. If no patch exists, implement network segmentation and restrict access to the vulnerable endpoint via firewall rules or disable the affected PHP component until a fix is available.

Fix this in Mozart Next 100 Firmware Scoped from the published advisory
  • Consultation4.0 h
  • Implementation6.0 h
  • Testing4.0 h
  • Review / QA2.0 h
16.0 hours of engineering $2,840
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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