CVE-2025-63228
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 · uneditedThe Mozart FM Transmitter web management interface on version WEBMOZZI-00287, contains an unauthenticated file upload vulnerability in the /upload_file.php endpoint. An attacker can exploit this by sending a crafted POST request with a malicious file (e.g., a PHP webshell) to the server. The uploaded file is stored in the /upload/ directory, enabling remote code execution and full system compromise.
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 confidenceThe Mozart FM Transmitter web management interface (WEBMOZZI-00287) has an unauthenticated file upload vulnerability in /upload_file.php. Attackers can send crafted POST requests with malicious files (e.g., PHP webshells) that get stored in the /upload/ directory, enabling remote code execution and full system compromise.
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 device modelCheck the device label, web interface header, or firmware information to confirm it is one of the following: Mozart Next 30, 50, 100, 300, 1000, 2000, 3000, or 3500Affected if The device is any Dbbroadcast Mozart Next series model listed in the affected products
-
Verify the web management interface is accessibleAttempt to reach the device web interface via its IP address in a browser or via curl http://<device_ip>Affected if The web interface responds and is reachable on the network
-
Confirm the vulnerable endpoint existsSend a request to http://<device_ip>/upload_file.php (e.g., curl -X POST http://<device_ip>/upload_file.php)Affected if The endpoint responds (even with an error) indicating the file exists and is accessible
-
Check for existing uploaded filesAccess http://<device_ip>/upload/ directory via browser or curl to list any files presentAffected if The /upload/ directory is accessible and contains files (especially .php, .phtml, or other executable file types)
-
Determine network exposure of the interfaceReview firewall rules, port scans, or network configuration to determine if port 80/443 (or the web interface port) is exposed to untrusted networksAffected if The web management interface is directly accessible from the internet or untrusted networks without VPN or authentication
If you operate any Dbbroadcast Mozart Next series device with an accessible web interface, you are affected because all firmware versions contain the vulnerable /upload_file.php endpoint.
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 dataImmediately disable or restrict access to the /upload_file.php endpoint, implement authentication, and add strict file type validation. Consider network segmentation to limit exposure and apply any available vendor firmware patches.
- Consultation3.0 h
- Implementation6.0 h
- Testing4.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 $4,224.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-63228 — 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-63228 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