# CVE-2021-1221: Cisco Webex Meetings and Cisco Webex Meetings Server Software Hyperlink Injection Vulnerability

> An authenticated attacker can inject malicious hyperlinks into meeting invitation emails, potentially tricking recipients into visiting attacker-controlled sites.

- **Severity:** Medium 4.1 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:C/C:N/I:L/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 4 Feb 2021
- **Updated:** 8 Nov 2024
- **Also known as:** GHSA-9qvw-hfpr-cvx6

## What is CVE-2021-1221?

CVE-2021-1221 is a medium-severity cross-site scripting vulnerability in Cisco Webex Meetings, published on 4 Feb 2021. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link.

### Official description

A vulnerability in the user interface of Cisco Webex Meetings and Cisco Webex Meetings Server Software could allow an authenticated, remote attacker to inject a hyperlink into a meeting invitation email. The vulnerability is due to insufficient input validation. An attacker could exploit this vulnerability by entering a URL into a field in the user interface. A successful exploit could allow the attacker to generate a Webex Meetings invitation email that contains a link to a destination of their choosing. Because this email is sent from a trusted source, the recipient may be more likely to click the link.

Weakness: CWE-74 (Improper Neutralization of Special Elements in Output Used by a Downstream Component), CWE-20 (Improper Input Validation)

## Which versions are affected by CVE-2021-1221?

It affects 2 products.


Products: Cisco Webex Meetings, Cisco Webex Meetings Server.

## How do I fix CVE-2021-1221?

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

## Is CVE-2021-1221 being exploited?

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

What it is: CVE-2021-1221 is a medium-severity cross-site scripting vulnerability in Cisco Webex Meetings, published on 4 Feb 2021. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2021-1221 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-2021-1221/ (Markdown: https://insights.sbomify.com/CVE-2021-1221/index.md)
```

## Sources

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

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