CVE-2026-20219: Cisco Webex Meetings · Insecure Direct Object Reference
Affects Cisco Webex MeetingsSource CVE Database V5
Not known to be exploited · CVSS 5.4 Medium.
Data as of 30 Oct 2026, 11:52 UTC
- EPSS
- 0.1% chance of exploitation in 30 days – higher than 6% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:NExploitation evidence
Disclosed: evidence found.
CVE published 6 May 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 30 Oct 2026.
What to do
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| CiscoCisco Webex Meetings | Affected
| Fixed in– |
| CiscoCisco Slido | Affected
| Fixed in– |
AI-suggested
Cisco has addressed this vulnerability in Cisco Slido, and no customer action is needed. Users should ensure they are running a fixed version of Cisco Webex Meetings or Cisco Slido as per Cisco's advisory. Since this is not a cloud service, customers should apply updates when available. Patch status is not explicitly stated but the vendor confirms the issue is resolved.
Description
A vulnerability in the REST API of Cisco Slido could have allowed an authenticated, remote attacker to access the social profile data of other users or affect quiz and poll results. Cisco has addressed this vulnerability in Cisco Slido and no customer action is needed. This vulnerability existed because of the presence of an insecure direct object reference. Prior to this vulnerability being addressed, an attacker could have exploited this vulnerability by sending a crafted request to the vulnerable API endpoint. A successful exploit could have allowed the attacker to view the social profiles of other users or affect quiz and poll results.