# CVE-2025-20291: Open redirect in Cisco Webex Meetings

> An attacker can redirect Webex Meetings users to malicious sites via crafted join URLs, facilitating phishing attacks.

- **Severity:** Medium 4.3 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:L/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 3 Sep 2025
- **Updated:** 3 Sep 2025
- **Also known as:** GHSA-65ch-j3gf-4m56

## What is CVE-2025-20291?

CVE-2025-20291 is a medium-severity vulnerability in Cisco Webex Meetings, published on 3 Sep 2025. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.

### Official description

A vulnerability in Cisco Webex Meetings could have allowed an unauthenticated, remote attacker to redirect a targeted Webex Meetings user to an untrusted website. Cisco has addressed this vulnerability in the Cisco Webex Meetings service, and no customer action is needed.

 This vulnerability existed because of insufficient validation of URLs that were included in a meeting-join URL. Prior to this vulnerability being addressed, an attacker could have exploited this vulnerability by including a URL to a website of their choosing in a specific value of a Cisco Webex Meetings join URL. A successful exploit could have allowed the attacker to redirect a targeted user to a website that was controlled by the attacker, possibly making the user more likely to believe the website was trusted by Webex and perform additional actions as part of phishing attacks.

Weakness: CWE-601 (URL Redirection to Untrusted Site)

## Which versions are affected by CVE-2025-20291?

It affects 1 product.


Products: Cisco Webex Meetings.

## How do I fix CVE-2025-20291?

No fix has been published for CVE-2025-20291 yet. Limit exposure of the affected software until one is available.

## Is CVE-2025-20291 being exploited?

There is no known exploitation of CVE-2025-20291 in the wild and no public exploit code.

## Other vulnerabilities in Cisco Webex Meetings

- [CVE-2017-12368](https://insights.sbomify.com/CVE-2017-12368/): Memory corruption in Cisco WebEx Recording Format and Advanced Recording Format Players (critical 9.6)
- [CVE-2017-12369](https://insights.sbomify.com/CVE-2017-12369/): Memory corruption in Cisco WebEx Recording Format and Advanced Recording Format Players (critical 9.6)
- [CVE-2017-12370](https://insights.sbomify.com/CVE-2017-12370/): Memory corruption in Cisco WebEx Recording Format and Advanced Recording Format Players (critical 9.6)
- [CVE-2017-12371](https://insights.sbomify.com/CVE-2017-12371/): Memory corruption in Cisco WebEx Recording Format and Advanced Recording Format Players (critical 9.6)
- [CVE-2017-12372](https://insights.sbomify.com/CVE-2017-12372/): Memory corruption in Cisco WebEx Recording Format and Advanced Recording Format Players (critical 9.6)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2025-20291 and fix it if it is affected.

What it is: CVE-2025-20291 is a medium-severity vulnerability in Cisco Webex Meetings, published on 3 Sep 2025. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2025-20291 in the wild and no public exploit code.

Affected product: Cisco Webex Meetings. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2025-20291/ (Markdown: https://insights.sbomify.com/CVE-2025-20291/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2025-20291
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2025-20291
- OSV: https://osv.dev/vulnerability/CVE-2025-20291

---
From sbomify Insights: https://insights.sbomify.com/CVE-2025-20291/
Summaries are generated and may contain mistakes; the official description above is the record.