CVE-2023-39293
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 Command Injection vulnerability has been identified in the MiVoice Office 400 SMB Controller through 1.2.5.23 which could allow a malicious actor to execute arbitrary commands within the context of the system.
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 confidenceA command injection vulnerability in MiVoice Office 400 SMB Controller (versions through 1.2.5.23) allows attackers to execute arbitrary commands on the underlying system with elevated privileges, exploiting insufficient input validation in the device firmware.
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 data<= 7.0.9281<= 1.2.5.23CVSS 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 MiVoice Office 400 installationLocate the Mitel MiVoice Office 400 system or SMB Controller device on your network. Check device documentation or network inventory for Mitel/Mitel-based phone system components.Affected if The system is a Mitel MiVoice Office 400 PBX or includes an SMB Controller module.
-
Check MiVoice Office 400 firmware versionAccess the device administrative interface or check system information panel. For the main PBX software, navigate to System Status or About section in the management console.Affected if The installed version is 7.0.9281 or lower.
-
Check SMB Controller firmware versionIf an SMB Controller device is deployed, access its web interface or administrative console and locate the firmware version information, typically found under Device Info, Status, or About pages.Affected if The SMB Controller firmware version is 1.2.5.23 or lower.
-
Assess network exposure of management interfacesReview firewall rules and network access controls to determine if the device administrative interfaces (web UI, CLI, or management ports) are accessible from untrusted networks or the internet.Affected if The SMB Controller management interface is exposed to untrusted networks or the internet.
The environment is affected if a MiVoice Office 400 system at version 7.0.9281 or lower, or an SMB Controller at firmware 1.2.5.23 or lower, is present and its management interface is network-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.
dbcve · scopedApply the vendor-supplied firmware patch to address the command injection vulnerability and restrict network access to the SMB Controller to trusted management stations.
Mivoice Office 400 SMB Controller Firmware: >1.2.5.23 | Mivoice Office 400: >7.0.9281 (contact Mitel for exact fixed versions)
- 1. Identify the exact current version of MiVoice Office 400 SMB Controller firmware currently installed
- 2. Identify the exact current version of MiVoice Office 400 software currently installed
- 3. Contact Mitel technical support or visit the official Mitel support portal to obtain the specific fixed firmware version (after 1.2.5.23) and software version (after 7.0.9281)
- 4. Download the appropriate firmware and software updates from Mitel's official support website
- 5. Follow Mitel's documented upgrade procedures to apply the firmware and software updates
- 6. After upgrading, verify the new versions are installed correctly
- 7. Confirm the command injection vulnerability is resolved by testing or consulting Mitel's release notes
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation3.0 h
- Implementation4.0 h
- Testing3.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 $3,408.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2023-39293 — 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-2023-39293 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