CVE-2020-24692
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 · uneditedThe Ignite portal in Mitel MiContact Center Business before 9.3.0.0 could allow an attacker to execute arbitrary scripts due to insufficient input validation, aka XSS. A successful exploit could allow an attacker to gain access to a user session.
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 confidenceA cross-site scripting (XSS) vulnerability exists in the Ignite portal of Mitel MiContact Center Business versions prior to 9.3.0.0 due to insufficient input validation. Attackers can inject arbitrary scripts into the portal that execute in the context of legitimate user sessions, potentially enabling session hijacking and unauthorized actions.
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< 9.3.0.0CVSS 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
- Local
- Complexity
- Low
- Privileges
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- None
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/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.
-
Confirm Mitel MiContact Center Business is installedLocate the installation directory on the system, typically found in Program Files or Program Files (x86) under Mitel. Check services.msc for MiContact Center Business servicesAffected if The product is not present on the system - no action needed
-
Identify the installed versionCheck the software version through the application UI (Help > About), or locate version information in the installation directory. Check registry keys under HKEY_LOCAL_MACHINE\SOFTWARE\Mitel if availableAffected if The installed version is lower than 9.3.0.0 - likely vulnerable
-
Verify the Ignite portal is accessibleAccess the Ignite web portal through a browser. The portal typically runs on port 8080 or 8443 (for example, https://server:8443/ignite)Affected if The Ignite portal is exposed and accessible to users without additional authentication controls
-
Review web server logs for XSS indicatorsExamine the Ignite portal web server logs for unusual request patterns, such as script tags, JavaScript event handlers, or encoded payloads in URL parametersAffected if Suspicious XSS payloads are found in the logs indicating potential exploitation attempts
You are affected if MiContact Center Business is installed with a version lower than 9.3.0.0 and the Ignite portal is accessible to users.
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 data9.3.0.0
Upgrade to Mitel MiContact Center Business version 9.3.0.0 or later. Additionally, implement proper input validation and output encoding for all user-supplied data in the Ignite portal.
- Consultation4.0 h
- Implementation8.0 h
- Testing4.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 $5,120.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2020-24692 — 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-2020-24692 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