CVE-2019-19371
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 cross-site scripting (XSS) vulnerability in the web conferencing component of Mitel MiCollab AWV before 8.1.2.2 could allow an unauthenticated attacker to conduct a reflected cross-site scripting (XSS) attack due to insufficient validation in the join meeting interface. A successful exploit could allow an attacker to execute arbitrary scripts.
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 reflected cross-site scripting (XSS) vulnerability exists in the web conferencing component of Mitel MiCollab AWV before version 8.1.2.2. The flaw is in the join meeting interface where insufficient input validation allows an unauthenticated attacker to inject malicious scripts that execute in the context of a victim's browser.
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<= 8.0.2.301>= 8.1, <= 8.1.1.11CVSS 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 checksWork through these to decide whether this CVE applies to you.
-
Confirm Mitel MiCollab AWV is installedCheck for MiCollab Audio/Web & Video services running on the system, or look for Mitel installation directories and web components typically found in the application's webroot (often under /opt/mitel/ or similar paths). Query the system for processes named 'micollab' or 'awv' or check the Mitel service management console.Affected if Mitel MiCollab AWV is present on the system
-
Identify the installed MiCollab AWV versionAccess the Mitel administration interface or check the version information file typically located in the MiCollab installation directory. The version may also be exposed in the web interface footer or via a version endpoint in the AWV web portal.Affected if The version is 8.0.2.301 or earlier, OR between 8.1.0 and 8.1.1.11 inclusive
-
Verify the join meeting web interface is accessibleAttempt to access the join meeting URL (typically /ucmweb/join or similar paths under the AWV web conferencing portal). Use a web browser or curl to check if the join meeting page loads and accepts meeting identifiers.Affected if The join meeting interface is exposed and reachable via HTTP/HTTPS
-
Test for reflected XSS in meeting identifier parametersSubmit a harmless test payload (such as a simple string like 'test123' or a benign XSS test string) in the meeting identifier field of the join page and inspect the response to see if input is reflected back without proper encoding. Compare the request parameters to how they appear in the HTML response.Affected if User-supplied input in the meeting join interface is reflected in the response without sanitization or encoding
A user is affected if Mitel MiCollab AWV versions 8.0.2.301 or earlier, or versions 8.1.0 through 8.1.1.11 are installed AND the web conferencing join meeting interface is accessible and reflects unsanitized user input.
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 dataUpgrade Mitel MiCollab AWV to version 8.1.2.2 or later. Additionally, implement robust input validation and output encoding on the join meeting interface to prevent XSS attacks.
- Consultation3.0 h
- Implementation6.0 h
- Testing4.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,512.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2019-19371 — 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-2019-19371 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