CVE-2025-67822
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 Provisioning Manager component of Mitel MiVoice MX-ONE 7.3 (7.3.0.0.50) through 7.8 SP1 (7.8.1.0.14) could allow an unauthenticated attacker to conduct an authentication bypass attack due to improper authentication mechanisms. A successful exploit could allow an attacker to gain unauthorized access to user or admin accounts in 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 · high confidenceAn authentication bypass vulnerability exists in the Provisioning Manager component of Mitel MiVoice MX-ONE versions 7.3.0.0.50 through 7.8.1.0.14. The flaw stems from improper authentication mechanisms that allow unauthenticated attackers to gain unauthorized access to user or admin accounts in the system.
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.3, < 7.8= 7.8CVSS 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
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/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.
-
Confirm MiVoice MX-ONE installationIdentify whether Mitel MiVoice MX-ONE is deployed in your environment by reviewing installed software, system inventory, or documentation.Affected if MiVoice MX-ONE is present in the environment
-
Determine the installed versionLocate and record the exact version number of the MiVoice MX-ONE installation. Consult system documentation, admin console, or version lookup methods provided by Mitel.Affected if The version number is 7.3.0.0.50 or higher, but lower than the fixed version
-
Compare version against affected rangeVerify whether the installed version falls within 7.3.0.0.50 through 7.8.1.0.14, or is version 7.8 exactly.Affected if The installed version is 7.3.0.0.50 through 7.8.1.0.14, or is version 7.8 (including 7.8.1.0.14)
-
Identify Provisioning Manager exposureDetermine whether the Provisioning Manager component is enabled and accessible. This may involve reviewing service configurations, open ports, or component status in the admin interface.Affected if Provisioning Manager is enabled and network-accessible
You are affected if MiVoice MX-ONE is installed with a version between 7.3.0.0.50 and 7.8.1.0.14 (or is version 7.8) and the Provisioning Manager component is exposed on the network.
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 · scoped7.8
Apply the vendor-provided security patch or upgrade to a fixed version of MiVoice MX-ONE. Until patched, restrict network access to the Provisioning Manager component to minimize exposure.
Mitel MiVoice MX-ONE version 7.9 or later (contact Mitel for specific fixed release)
- Identify the current Mitel MiVoice MX-ONE version by checking the Provisioning Manager component or system information
- Contact Mitel support or visit the official Mitel support portal to obtain the latest secure release (version 7.9 or later)
- Download the upgrade package for the target version
- Review the upgrade documentation and release notes for any prerequisites
- Perform a full backup of the current system configuration
- Schedule a maintenance window for the upgrade process
- Follow the official Mitel upgrade procedure to apply the patch to the Provisioning Manager component
- Verify the upgrade was successful by checking the version number
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation3.0 h
- Implementation6.0 h
- Testing6.0 h
- Review / QA3.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,992.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-67822 — 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-67822 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