dbcve.org
Webex TeamsApplication · Cisco

CVE-2025-20236

HIGH · 8.8 CVSS v3.1 Published 2025-04-16
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
95/100
Remediation priority · Urgent
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 custom URL parser of Cisco Webex App could allow an unauthenticated, remote attacker to persuade a user to download arbitrary files, which could allow the attacker to execute arbitrary commands on the host of the targeted user. This vulnerability is due to insufficient input validation when Cisco Webex App processes a meeting invite link. An attacker could exploit this vulnerability by persuading a user to click a crafted meeting invite link and download arbitrary files. A successful exploit could allow the attacker to execute arbitrary commands with the privileges of the targeted user.

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

A vulnerability in the custom URL parser of Cisco Webex App allows insufficient input validation when processing meeting invite links. An attacker can craft malicious meeting invite links that persuade users to download arbitrary files, potentially leading to arbitrary command execution with the privileges of the targeted user.

MitigationApply the vendor patch from Cisco for Cisco Webex App once released; users should avoid clicking untrusted meeting invite links until the patch is 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 TeamsApplication
Affected:= 44.6= 44.6.0.29928= 44.6.0.30148= 44.7= 44.7.0.30141= 44.7.0.30285

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
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H

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. Confirm Cisco Webex App installation
    Check for Cisco Webex App installation - on Windows look in Program Files for 'Cisco Webex' folder, or check for Webex Teams application in installed programs. On macOS, check /Applications for 'Cisco Webex Apps' folder.
    Affected if Cisco Webex App is not installed on the system
  2. Determine installed version number
    Open Cisco Webex App, click on your profile picture or settings, then navigate to Help > About Cisco Webex or similar. Alternatively, check the application properties in Windows Control Panel > Programs and Features, or on macOS right-click the app and select Get Info.
    Affected if The installed version matches any of these: 44.6, 44.6.0.29928, 44.6.0.30148, 44.7, 44.7.0.30141, or 44.7.0.30285
  3. Verify URL handler registration
    Check if Webex URL protocol handler (webex://) is registered on the system. On Windows, run 'assoc | findstr webex' or check registry under HKCR\webex. On macOS, check ~/Library/Application\ Support/com.cisco.webexmeetingsapp or run 'lsregister | grep webex'.
    Affected if The Webex URL protocol handler is registered and active on the system

You are affected if Cisco Webex App is installed AND its version is one of: 44.6, 44.6.0.29928, 44.6.0.30148, 44.7, 44.7.0.30141, or 44.7.0.30285, and the application processes meeting invite links through its custom URL parser.

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

Apply the vendor patch from Cisco for Cisco Webex App once released; users should avoid clicking untrusted meeting invite links until the patch is applied.

Fix this in Webex Teams Scoped from the published advisory
  • Consultation3.0 h
  • Implementation2.0 h
  • Testing2.0 h
  • Review / QA1.0 h
8.0 hours of engineering $1,440
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-20236 — 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-2025-20236 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