CVE-2025-66256
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 · uneditedUnauthenticated Arbitrary File Upload (patch_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 Unrestricted file upload in patch_contents.php allows uploading malicious files. The `/var/tdf/patch_contents.php` endpoint allows unauthenticated arbitrary file uploads without file type validation, MIME checking, or size restrictions beyond 16MB, enabling attackers to upload malicious files.
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 confidenceUnauthenticated arbitrary file upload vulnerability in /var/tdf/patch_contents.php on Mozart FM Transmitter devices allows remote attackers to upload any file type without authentication, file type validation, or MIME checking. With a 16MB size limit being the only constraint, attackers can upload malicious PHP shells or other payloads leading to remote code execution.
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 dataall versionsall versionsall versionsall versionsall versionsall versionsall versionsall versionsCVSS 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 checksWork through these to decide whether this CVE applies to you.
-
Identify Mozart Transmitter device model and firmware versionAccess the device web interface or check system information to confirm the device is a Dbbroadcast Mozart Next model (100, 1000, 2000, 30, 300, 3000, 3500, or 50) and note the firmware versionAffected if Device is any Dbbroadcast Mozart Next model listed in the affected products regardless of firmware version
-
Verify web interface accessibilityAttempt to access the device web interface via HTTP/HTTPS on the configured management IPAffected if Web interface is accessible and responds to requests
-
Check if patch_contents.php endpoint existsRequest the URL path /var/tdf/patch_contents.php on the device web server (e.g., http://[device-ip]/var/tdf/patch_contents.php)Affected if The endpoint responds (even with an error) indicating the file exists on the system
-
Test authentication requirement on upload endpointSend a crafted file upload request to /var/tdf/patch_contents.php without providing any authentication credentials (e.g., using curl or a browser developer tool)Affected if The request succeeds without requiring login or authentication tokens
-
Verify lack of file type restrictionsSend an upload request containing a file with a potentially malicious extension (such as .php, .phtml, or .exe) to /var/tdf/patch_contents.php and observe if it is accepted without rejectionAffected if The upload accepts files without validating the file extension or MIME type
-
Check upload directory configurationExamine the web server configuration or attempt to access an uploaded file via the web to determine if uploaded files are stored in a web-accessible directory with script execution enabledAffected if Uploaded files are stored in a web-accessible directory and can be executed as scripts
A user is affected if they have a Dbbroadcast Mozart Next device with an accessible web interface where /var/tdf/patch_contents.php accepts unauthenticated file uploads without type restrictions.
Generated from the published advisory. Verify against your own configuration.
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 dataImplement authentication requirements and strict allowlist-based file type/MIME validation on the upload endpoint, and store uploaded files outside web-accessible directories or disable script execution in the upload directory.
- Consultation2.0 h
- Implementation3.0 h
- Testing3.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,800.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-66256 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2025-66256 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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