CVE-2025-66259
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 · uneditedAuthenticated Root Remote Code Execution via improrer user input filtering 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 in main_ok.php user supplied data/hour/time is passed directly into date shell command
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 confidenceAuthenticated command injection vulnerability in main_ok.php of Mozart FM Transmitter allows attackers to inject arbitrary commands via user-supplied hour/time parameters that are passed directly to a shell 'date' command without sanitization, resulting in root-level 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 your Mozart FM Transmitter modelCheck the device label, web interface header, or system information page for the exact model name (Mozart Next 100, 1000, 2000, 30, 300, 3000, 3500, or 50)Affected if The model is any of the Dbbroadcast Mozart Next series (100, 1000, 2000, 30, 300, 3000, 3500, 50)
-
Verify the web management interface is accessibleAttempt to access the device web interface by entering the device IP address in a browser. Look for the login page or any mozart/dbbroadcast branded interfaceAffected if The web interface is reachable over HTTP/HTTPS on the network
-
Check for the vulnerable main_ok.php scriptIf the web interface is accessible, try navigating to main_ok.php (for example: http://[device-ip]/main_ok.php or check the application's PHP file list)Affected if The main_ok.php script exists on the web server and is accessible
-
Confirm authentication is requiredObserve whether the web interface requires login credentials before allowing access to time/clock settings or the main_ok.php endpointAffected if The interface allows authenticated users to access time parameter settings
-
Assess network exposure of the management interfaceReview firewall rules, port scans, or network configurations to determine if the web management port (typically 80 or 443) is exposed to untrusted networksAffected if The web interface is accessible from outside the trusted network
You are affected if you operate any Dbbroadcast Mozart Next series FM transmitter (100, 1000, 2000, 30, 300, 3000, 3500, or 50) with its web management interface accessible on the network, since all firmware versions contain the vulnerable main_ok.php script.
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 strict input validation and sanitization for all user-supplied parameters before shell command execution; replace direct shell command calls with safe API alternatives or parameterized methods.
- Consultation4.0 h
- Implementation8.0 h
- Testing8.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $6,656.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-66259 — 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-66259 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