# CVE-2020-27126: Cisco Webex Meetings API Cross-Site Scripting Vulnerability

> Unauthenticated attackers can execute cross-site scripting attacks via malicious links to steal sensitive browser-based information from Cisco Webex Meetings users.

- **Severity:** Medium 6.1 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/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:** 18 Nov 2020
- **Updated:** 13 Nov 2024
- **Also known as:** GHSA-g7h4-mcf5-vrf5

## What is CVE-2020-27126?

CVE-2020-27126 is a medium-severity cross-site scripting vulnerability in Cisco Webex Meetings, published on 18 Nov 2020. 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 an API of Cisco Webex Meetings could allow an unauthenticated, remote attacker to conduct cross-site scripting attacks. The vulnerability is due to improper validation of user-supplied input to an application programmatic interface (API) within Cisco Webex Meetings. An attacker could exploit this vulnerability by convincing a targeted user to follow a link designed to submit malicious input to the API used by Cisco Webex Meetings. A successful exploit could allow the attacker to conduct cross-site scripting attacks and potentially gain access to sensitive browser-based information from the system of a targeted user.

Weakness: CWE-79 (Improper Neutralization of Input During Web Page Generation), CWE-80 (Improper Neutralization of Script-Related HTML Tags in a Web Page)

## Which versions are affected by CVE-2020-27126?

It affects 1 product.


Products: Cisco Webex Meetings.

## How do I fix CVE-2020-27126?

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

## Is CVE-2020-27126 being exploited?

There is no known exploitation of CVE-2020-27126 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-2020-27126 and fix it if it is affected.

What it is: CVE-2020-27126 is a medium-severity cross-site scripting vulnerability in Cisco Webex Meetings, published on 18 Nov 2020. 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-2020-27126 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-2020-27126/ (Markdown: https://insights.sbomify.com/CVE-2020-27126/index.md)
```

## Sources

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

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