CVE-2025-47188
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 · uneditedA 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 conduct a command injection attack due to insufficient parameter sanitization. A successful exploit could allow an attacker to execute arbitrary commands within the context of the phone, leading to disclosure or modification of sensitive configuration data or affecting device availability and operation.
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 · moderate confidenceMitel 6800/6900 Series SIP phones and 6970 Conference Units contain a command injection vulnerability in the web interface or other management interface. The vulnerability stems from insufficient sanitization of user-supplied parameters, allowing an unauthenticated attacker to inject and execute arbitrary operating system commands on the affected device. This could enable full compromise of the phone, including access to configuration data, call recordings, and network access through the compromised device.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
CVSS 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
- Low
- Integrity
- Low
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:N
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 Mitel phone models on your networkInventory your network devices to locate Mitel 6800 Series, 6900 Series SIP phones, or 6970 Conference Units. Check device labels, DHCP lease logs, or network scan results for these specific model identifiers.Affected if You have any Mitel 6800/6900 Series SIP phones or 6970 Conference Units deployed.
-
Check firmware versionAccess the phone web interface or admin menu, or query the device via SIP/management protocol. Navigate to the firmware or system information section to retrieve the current installed firmware version.Affected if The installed firmware version is earlier than 6.4 SP4.
-
Verify web management interface statusCheck if the web-based administration interface is enabled on the device. This is typically found in the device settings under 'Web Server', 'HTTP/HTTPS', or 'Management Interface' options.Affected if The web management interface is enabled and accessible.
-
Assess network exposure of management interfaceDetermine if the web management interface is reachable from untrusted networks. Use network scans, firewall rules, or ACL configurations to identify whether port 80/443 on these devices is exposed to the internet or unauthorized VLANs.Affected if The management interface is reachable from networks outside your trusted administrative zone.
You are affected if you have Mitel 6800/6900 Series phones or 6970 Conference Units running firmware versions earlier than 6.4 SP4 with the web management interface enabled and accessible.
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 dataApply vendor-supplied firmware patches (6.4 SP4 or later). If patches are unavailable, restrict network access to management interfaces using firewalls or ACLs, and disable remote management capabilities where possible.
- Consultation8.0 h
- Implementation16.0 h
- Testing12.0 h
- Review / QA6.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $11,776.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-47188 — 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-47188 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