Webex MeetingsApplication · Cisco
CVE-2022-20654
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 web-based interface of Cisco Webex Meetings could allow an unauthenticated, remote attacker to conduct a cross-site scripting (XSS) attack against a user of the web-based interface. This vulnerability is due to insufficient validation of user-supplied input by the web-based interface of Cisco Webex Meetings. An attacker could exploit this vulnerability by persuading a user of the interface to click a maliciously crafted link. A successful exploit could allow the attacker to execute arbitrary script code in the context of the affected interface or access sensitive, browser-based information.Cisco has released software updates that address this vulnerability. There are no workarounds that address this vulnerability.
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 confidenceThis is a stored XSS vulnerability in Cisco Webex Meetings' web-based interface where insufficient validation of user-supplied input allows an attacker to inject malicious scripts via a crafted link. When users click the malicious link, the attacker can execute arbitrary JavaScript in the context of the user's session, potentially stealing session cookies or other sensitive browser-based information.
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
Webex MeetingsApplication
= 39.6= 39.7= 39.7.4= 39.7.7= 39.8= 39.8.2= 39.8.3= 39.8.4= 39.9= 39.9.1= 39.10= 39.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.
-
Identify if Cisco Webex Meetings is deployedDetermine whether your organization hosts or manages a Cisco Webex Meetings server. This vulnerability affects the server-side web interface, not the client applications.Affected if You host or manage a Cisco Webex Meetings server in your environment
-
Check the installed Webex Meetings server versionLog into the Webex Meetings administration interface or check the server's version information. The exact method varies by deployment but is typically found in the admin console under 'Site Administration' or by querying the server directly.Affected if The installed version matches one of: 39.6, 39.7, 39.7.4, 39.7.7, 39.8, 39.8.2, 39.8.3, 39.8.4, 39.9, 39.9.1, 39.10, or 39.11
-
Verify the web-based interface is accessibleConfirm that the Webex Meetings web portal is accessible to users. This vulnerability exploits the web interface where users interact with meeting links and content.Affected if The web interface is enabled and reachable at your Webex URL (typically at /webex/ or similar paths)
-
Review access logs for suspicious link patternsExamine web server access logs for unusual or malicious URL parameters being submitted to the meeting interface, particularly in areas where user-supplied input is stored and displayed back to other users.Affected if Unusual crafted URLs containing script tags or JavaScript payloads are present in request logs
Your environment is affected if you run an on-premises or hosted Cisco Webex Meetings server at version 39.6 through 39.11 and users access the web interface.
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 dataApply the Cisco software updates that address this vulnerability. Since no workarounds are available, patching is the only remediation path. Users should be warned about clicking untrusted links.
Fix this in Webex Meetings
Scoped from the published advisory
- Consultation2.0 h
- Implementation4.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 $3,328.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-20654 — 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-2022-20654 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