Webex Meetings OnlineApplication · Cisco

CVE-2020-3472

MEDIUM · 5.0 CVSS v3.1 Published 2020-08-17
Fix available
A fix is available. Upgrade to 40.7.0 or later.
See remediation →
56/100
Remediation priority · Elevated
Remotely reachable Zero-click

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 vulnerability in the contacts feature of Cisco Webex Meetings could allow an authenticated, remote attacker with a legitimate user account to access sensitive information. The vulnerability is due to improper access restrictions on users who are added within user contacts. An attacker on one Webex Meetings site could exploit this vulnerability by sending specially crafted requests to the Webex Meetings site. A successful exploit could allow the attacker to view the details of users on another Webex site, including user names and email addresses.

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

An improper access control vulnerability in the contacts feature of Cisco Webex Meetings allows an authenticated attacker with a valid user account on one Webex site to view sensitive user details (names, email addresses) from another Webex site by sending specially crafted requests. The vulnerability stems from insufficient access restrictions on users added within user contacts, enabling cross-site information disclosure.

MitigationApply the vendor-supplied patch from Cisco; verify that Webex Meetings sites are updated to a patched version. This is a server-side fix requiring Cisco's update rather than client-side configuration changes.

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 Meetings OnlineApplication
Affected:< 40.7.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
Low
User interaction
None
Scope
Changed
Confidentiality
Low
Integrity
None
Availability
None

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:L/I:N/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. Locate your Webex Meetings site version
    Log into your Webex site administration console (typically at sites.webex.com or your organization's custom Webex URL). Navigate to Site Administration > Site Information. The current Webex Meetings version is displayed in the Site Version or Build Number field.
    Affected if The displayed version number is lower than 40.7.0 (for example, 40.6.x, 40.5.x, or earlier)
  2. Confirm you use Webex Meetings Online
    Verify that your organization uses Cisco's hosted Webex Meetings service (Webex Meetings Online) rather than an on-premises Webex Meetings Server installation. Check your subscription details or ask your Webex administrator.
    Affected if You are using the cloud-hosted Cisco Webex Meetings Online service and your site version is below 40.7.0
  3. Identify if the contacts feature is active
    Log into your Webex Meetings account as a standard user. Navigate to the Contacts or Address Book section within the Webex client or web interface. Confirm the contacts feature is accessible and functional.
    Affected if The contacts feature is enabled and you can add or view user contacts on your Webex site, and your site version is below 40.7.0

Your organization is affected if your Webex Meetings Online site is running a version earlier than 40.7.0 and users have access to the contacts feature.

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 40.7.0 or later
Fixed in 40.7.0
Interim mitigation

Apply the vendor-supplied patch from Cisco; verify that Webex Meetings sites are updated to a patched version. This is a server-side fix requiring Cisco's update rather than client-side configuration changes.

Fix this in Webex Meetings Online Scoped from the published advisory
  • Consultation1.0 h
  • Testing1.0 h
  • Review / QA1.0 h
3.0 hours of engineering $750
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2020-3472 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