# CVE-2025-63228: File upload in n/a

> Unauthenticated attackers can upload malicious files to the FM Transmitter web interface, leading to remote code execution and full system compromise.

- **Severity:** Critical 9.8 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 18 Nov 2025
- **Updated:** 19 Nov 2025
- **Also known as:** GHSA-rp7m-4f5j-m5wj

## What is CVE-2025-63228?

CVE-2025-63228 is a critical vulnerability in n/a, published on 18 Nov 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

The 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.

Weakness: CWE-434 (Unrestricted Upload of File with Dangerous Type)

## Which versions are affected by CVE-2025-63228?

It affects 22 products.


Products: Dbbroadcast Mozart Dds Next 1000 Firmware, Dbbroadcast Mozart Dds Next 100 Firmware, Dbbroadcast Mozart Dds Next 2000 Firmware, Dbbroadcast Mozart Dds Next 3000 Firmware, Dbbroadcast Mozart Dds Next 300 Firmware, Dbbroadcast Mozart Dds Next 30 Firmware, Dbbroadcast Mozart Dds Next 3500 Firmware, Dbbroadcast Mozart Dds Next 500 Firmware, Dbbroadcast Mozart Dds Next 50 Firmware, Dbbroadcast Mozart Dds Next 6000 Firmware, Dbbroadcast Mozart Dds Next 7000 Firmware, Dbbroadcast Mozart Next 1000 Firmware, Dbbroadcast Mozart Next 100 Firmware, Dbbroadcast Mozart Next 2000 Firmware, Dbbroadcast Mozart Next 3000 Firmware, Dbbroadcast Mozart Next 300 Firmware, Dbbroadcast Mozart Next 30 Firmware, Dbbroadcast Mozart Next 3500 Firmware, Dbbroadcast Mozart Next 500 Firmware, Dbbroadcast Mozart Next 50 Firmware and 2 more.

## How do I fix CVE-2025-63228?

No fix has been published for CVE-2025-63228 yet. Limit exposure of the affected software until one is available.

## Is CVE-2025-63228 being exploited?

There is no known exploitation of CVE-2025-63228 in the wild and no public exploit code.

## Other vulnerabilities in n/a

- [CVE-2025-66253](https://insights.sbomify.com/CVE-2025-66253/): Unauthenticated OS Command Injection (start_upgrade.php) (critical 9.9)
- [CVE-2025-66255](https://insights.sbomify.com/CVE-2025-66255/): Unauthenticated Arbitrary File Upload (upgrade_contents.php) (critical 9.9)
- [CVE-2025-66256](https://insights.sbomify.com/CVE-2025-66256/): Unauthenticated Arbitrary File Upload (patch_contents.php) (critical 9.9)
- [CVE-2025-66261](https://insights.sbomify.com/CVE-2025-66261/): Unauthenticated OS Command Injection (restore_settings.php) (critical 9.9)
- [CVE-2025-66259](https://insights.sbomify.com/CVE-2025-66259/): Authenticated Root Remote Code Execution through improper filtering of HTTP post request parameters (critical 9.3)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2025-63228 and fix it if it is affected.

What it is: CVE-2025-63228 is a critical vulnerability in n/a, published on 18 Nov 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2025-63228 in the wild and no public exploit code.

Affected product: n/a. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2025-63228/ (Markdown: https://insights.sbomify.com/CVE-2025-63228/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2025-63228
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2025-63228
- OSV: https://osv.dev/vulnerability/CVE-2025-63228

---
From sbomify Insights: https://insights.sbomify.com/CVE-2025-63228/
Summaries are generated and may contain mistakes; the official description above is the record.