dbcve.org
Micontact Center EnterpriseApplication · Mitel

CVE-2021-26714

CRITICAL · 9.8 CVSS v3.1 Published 2021-03-29
Fix available
A fix is available. Upgrade to 9.4 or later.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable No privileges Zero-click

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 · unedited
The Enterprise License Manager portal in Mitel MiContact Center Enterprise before 9.4 could allow a user to access restricted files and folders due to insufficient access control. A successful exploit could allow an attacker to view and modify application data via Directory Traversal.

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 confidence

A directory traversal vulnerability exists in the Enterprise License Manager portal of Mitel MiContact Center Enterprise versions prior to 9.4. The portal fails to properly validate path traversal sequences in user-supplied input, allowing authenticated or unauthenticated attackers to use '..' sequences to escape the intended directory and access or modify arbitrary files within the application filesystem.

MitigationUpgrade to Mitel MiContact Center Enterprise version 9.4 or later. If immediate patching is not possible, implement input validation filters to reject path traversal sequences ('..') and enforce strict allow-list access controls on the license manager portal.

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
Micontact Center EnterpriseApplication
Affected:< 9.4

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
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 checks

Work through these to decide whether this CVE applies to you.

  1. Identify installed MiContact Center Enterprise version
    Locate the installed version through the product's administration interface, license information, or installed packages. Common locations include the program files directory, about/status pages in the web interface, or system inventory tools.
    Affected if The installed version is any release prior to 9.4 (e.g., 9.3.x, 9.2.x, earlier versions)
  2. Confirm Enterprise License Manager portal is enabled
    Access the license manager portal URL (typically /license-manager or /elm on the application host) via HTTP/HTTPS to determine if the interface is active and responding.
    Affected if The license manager portal is accessible and responds to requests
  3. Verify network accessibility of the license manager portal
    Check network listening ports and firewall rules to determine if the license manager portal is exposed to network access, either internally or externally.
    Affected if The portal is reachable from network segments beyond the intended administrative scope
  4. Inspect application logs for traversal attempts
    Review web server and application logs for requests containing '../' sequences targeting the license manager endpoint.
    Affected if Historical or current logs show traversal patterns like '..' or path traversal sequences in license manager requests

A user is affected if MiContact Center Enterprise version is below 9.4 AND the Enterprise License Manager portal is accessible, regardless of authentication status.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 · scoped
Upgrade available Upgrade to 9.4 or later
Fixed in 9.4
Interim mitigation

Upgrade to Mitel MiContact Center Enterprise version 9.4 or later. If immediate patching is not possible, implement input validation filters to reject path traversal sequences ('..') and enforce strict allow-list access controls on the license manager portal.

Recommended fix Moderate confidence

9.4

  1. Back up all current configuration data and application databases before initiating the upgrade
  2. Verify that your current system meets all prerequisites for version 9.4 as documented in Mitel compatibility guides
  3. Download the MiContact Center Enterprise version 9.4 (or latest stable release) from Mitel's official support portal at www.mitel.com
  4. Follow Mitel's documented upgrade procedure for MiContact Center Enterprise, ensuring the Enterprise License Manager component is included in the upgrade
  5. After completing the upgrade, verify the Enterprise License Manager portal is functioning normally
  6. Confirm the directory traversal vulnerability is resolved by attempting to access restricted paths through the portal (or use vulnerability scanning tools)
  7. Test critical business functions in the contact center to ensure no regressions
Caveat No specific breaking changes documented in provided material; standard enterprise upgrade precautions apply (backup, testing in staging recommended)

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Micontact Center Enterprise Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA1.0 h
10.0 hours of engineering $1,750
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,800.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2021-26714 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2021-26714 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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