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

> Unauthenticated attackers can upload arbitrary WAV files to Mitel SIP phones, potentially exhausting storage and causing denial of service.

- **Severity:** High 7.5 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/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:** 23 Jul 2025
- **Updated:** 29 Jul 2025
- **Also known as:** GHSA-676m-p53v-8qw7

## What is CVE-2025-47187?

CVE-2025-47187 is a high-severity vulnerability in n/a, published on 23 Jul 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

A vulnerability in the Mitel 6800 Series, 6900 Series, and 6900w Series SIP Phones through 6.4 SP4 (R6.4.0.4006), and the 6970 Conference Unit through 6.4 SP4 (R6.4.0.4006) or version V1 R0.1.0, could allow an unauthenticated attacker to perform a file upload attack due to missing authentication mechanisms. A successful exploit could allow an attacker to upload arbitrary WAV files, which may potentially exhaust the phone’s storage without affecting the phone's availability or operation.

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

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


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

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

## Is CVE-2025-47187 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2025-47187 is a high-severity vulnerability in n/a, published on 23 Jul 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-47187 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-47187/ (Markdown: https://insights.sbomify.com/CVE-2025-47187/index.md)
```

## Sources

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

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