# CVE-2025-66252: Infinite Loop Denial of Service via Failed File Deletion

> An attacker can cause a denial of service by triggering an infinite loop in the FM transmitter's file deletion logic when unlink operations fail.

- **Severity:** High 8.4 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:H/UI:N/VC:N/VI:H/VA:H/SC:N/SI:H/SA:H`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 26 Nov 2025
- **Updated:** 1 Dec 2025
- **Also known as:** GHSA-5rfv-6ff9-rm8q

## What is CVE-2025-66252?

CVE-2025-66252 is a high-severity denial of service vulnerability in DB Electronica Telecomunicazioni S.p.A. Mozart FM Transmitter, published on 26 Nov 2025. An attacker needs administrator access to exploit it, with no action from the victim.

### Official description

Infinite Loop Denial of Service via Failed File Deletion 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 Infinite loop when unlink() fails in status_contents.php causing DoS. Due to the fact that the unlink operation is done in a while loop; if an immutable file is specified or otherwise a file in which the process has no permissions to delete; it would repeatedly attempt to do in a loop.

Weakness: CWE-835 (Loop with Unreachable Exit Condition)

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

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-66252?

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

## Is CVE-2025-66252 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-66252 exists.

## Other vulnerabilities in DB Electronica Telecomunicazioni S.p.A. Mozart FM Transmitter

- [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-63228](https://insights.sbomify.com/CVE-2025-63228/): File upload in n/a (critical 9.8)

## Fix prompt for AI coding agents

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

What it is: CVE-2025-66252 is a high-severity denial of service vulnerability in DB Electronica Telecomunicazioni S.p.A. Mozart FM Transmitter, published on 26 Nov 2025. An attacker needs administrator access to exploit it, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-66252 exists.

Affected product: DB Electronica Telecomunicazioni S.p.A. Mozart FM Transmitter. 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-66252/ (Markdown: https://insights.sbomify.com/CVE-2025-66252/index.md)
```

## Sources

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

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