dbcve.org
Mivoice ConnectApplication · Mitel

CVE-2020-12679

MEDIUM · 6.1 CVSS v3.1 Published 2020-05-07
Fix available
A fix is available. Upgrade to 21.90.9743.0 or later.
See remediation →
68/100
Remediation priority · Elevated
Remotely reachable No privileges

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
A reflected cross-site scripting (XSS) vulnerability in the Mitel ShoreTel Conference Web Application 19.50.1000.0 before MiVoice Connect 18.7 SP2 allows remote attackers to inject arbitrary JavaScript and HTML via the PATH_INFO to home.php.

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 reflected cross-site scripting (XSS) vulnerability exists in Mitel ShoreTel Conference Web Application (versions before MiVoice Connect 18.7 SP2). The vulnerability resides in the home.php component, where user-supplied input via PATH_INFO is not properly sanitized before being reflected back in the HTTP response, allowing attackers to inject arbitrary JavaScript and HTML into the page.

MitigationApply the vendor patch (MiVoice Connect 18.7 SP2 or later) to remediate this vulnerability. As a temporary control, implement input validation and output encoding on the PATH_INFO parameter in home.php, or deploy a WAF rule to block malicious XSS payloads.

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
Mivoice ConnectApplication
Affected:< 21.90.9743.0
Shoretel Conference WebApplication
Affected:= 19.50.1000.0

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
Required
Scope
Changed
Confidentiality
Low
Integrity
Low
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/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 checks

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

  1. Identify installed MiVoice Connect version
    Access the admin interface or check the software installation directory for version information. On Windows, check 'C:\Program Files\Mitel\MiVoice Connect\' or look in the Windows registry under 'HKLM\SOFTWARE\Mitel\MiVoice Connect' for the version key. On Linux, check '/opt/mitel/voice/' or the package manager listing.
    Affected if The installed version is below 21.90.9743.0 (for MiVoice Connect)
  2. Identify installed ShoreTel Conference Web version
    Check the ShoreTel Conference Web installation for version information, typically found in the application admin panel or in the installation directory's version file.
    Affected if The installed version is 19.50.1000.0 (for ShoreTel Conference Web)
  3. Locate home.php component
    Search the web server document root for the home.php file, commonly found in paths like '/conference/home.php', '/web/home.php', or '/home.php'. Verify the file exists and is web-accessible.
    Affected if The home.php file exists in the web-accessible directory and handles PATH_INFO requests
  4. Test PATH_INFO for XSS reflection
    Send an HTTP GET request to home.php with a test payload in the PATH_INFO, for example: GET /home.php/<script>alert('XSS')</script> HTTP/1.1. Inspect the response body to see if the script tag is returned without encoding or sanitization.
    Affected if The reflected response contains the raw <script> tag or other unencoded HTML/JavaScript from the PATH_INFO input

You are affected if your installed MiVoice Connect version is below 21.90.9743.0 (or equals 19.50.1000.0 for ShoreTel Conference Web) AND the home.php component reflects PATH_INFO input without sanitization.

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.

From vendor data
Upgrade available Upgrade to 21.90.9743.0 or later
Fixed in 21.90.9743.0
Interim mitigation

Apply the vendor patch (MiVoice Connect 18.7 SP2 or later) to remediate this vulnerability. As a temporary control, implement input validation and output encoding on the PATH_INFO parameter in home.php, or deploy a WAF rule to block malicious XSS payloads.

Fix this in Mivoice Connect Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing4.0 h
  • Review / QA2.0 h
15.0 hours of engineering $2,640
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2020-12679 — 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-2020-12679 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