dbcve.org
Webex MeetingsApplication · Cisco

CVE-2021-34743

HIGH · 7.1 CVSS v3.1 Published 2021-10-21
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
78/100
Remediation priority · High
Remotely reachable No privileges

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 application integration feature of Cisco Webex Software could allow an unauthenticated, remote attacker to authorize an external application to integrate with and access a user's account without that user's express consent. This vulnerability is due to improper validation of cross-site request forgery (CSRF) tokens. An attacker could exploit this vulnerability by convincing a targeted user who is currently authenticated to Cisco Webex Software to follow a link designed to pass malicious input to the Cisco Webex Software application authorization interface. A successful exploit could allow the attacker to cause Cisco Webex Software to authorize an application on the user's behalf without the express consent of the user, possibly allowing external applications to read data from that user's profile.

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

This is a CSRF (Cross-Site Request Forgery) vulnerability in Cisco Webex's application integration feature. The application authorization interface fails to properly validate CSRF tokens, allowing an unauthenticated remote attacker to trick an authenticated user into unknowingly authorizing a malicious external application to access their Webex account and profile data.

MitigationThe vendor should implement proper CSRF token validation on all authorization endpoints. Users should avoid clicking untrusted links while authenticated to Webex. Cisco has released patches that should be applied.

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
Affected:all versions

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
None
User interaction
Required
Scope
Unchanged
Confidentiality
Low
Integrity
High
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:L/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 checks

Work through these to decide whether this CVE applies to you.

  1. Identify Cisco Webex Meetings version
    Locate the Webex Meetings installation and retrieve its version number through the admin console, installation directory, or version command specific to your deployment
    Affected if Any version of Cisco Webex Meetings is installed, as all versions are affected by this vulnerability
  2. Confirm application authorization feature is enabled
    Verify that the Webex application integration or third-party application authorization feature is active in your Webex environment settings or admin configuration
    Affected if The application integration/authorization feature is enabled and users can authorize external applications to access their Webex account
  3. Check for CSRF protection on authorization endpoints
    Inspect the HTTP responses and form submissions during the application authorization flow to verify whether anti-CSRF tokens or SameSite cookies are present and properly validated
    Affected if The authorization endpoints do not validate CSRF tokens or lack SameSite cookie attributes, allowing requests to proceed without proper token verification
  4. Review authorization request behavior
    Attempt to initiate an application authorization request from an external context (such as a different origin) and observe whether the request is processed without requiring valid anti-CSRF token validation
    Affected if Authorization requests from cross-origin contexts are accepted without proper CSRF token validation, indicating the vulnerability is present

A Cisco Webex Meetings deployment is affected if it has the application authorization feature enabled and the authorization endpoints do not properly validate CSRF tokens during the authorization flow.

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
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

The vendor should implement proper CSRF token validation on all authorization endpoints. Users should avoid clicking untrusted links while authenticated to Webex. Cisco has released patches that should be applied.

Fix this in Webex Meetings Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA4.0 h
22.0 hours of engineering $3,860
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2021-34743 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

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-2021-34743 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