# CVE-2023-20209: Command injection in Cisco TelePresence Video Communication Server (VCS) Expressway

> Authenticated attackers can execute arbitrary commands with root privileges via the web management interface of Cisco Expressway and VCS devices.

- **Severity:** Medium 6.5 (`CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 16 Aug 2023
- **Updated:** 16 Dec 2025
- **Also known as:** GHSA-fqmx-hq6j-36x9

## What is CVE-2023-20209?

CVE-2023-20209 is a medium-severity command injection vulnerability in Cisco TelePresence Video Communication Server (VCS) Expressway, published on 16 Aug 2023. An attacker needs administrator access to exploit it, with no action from the victim.

### Official description

A vulnerability in the web-based management interface of Cisco Expressway Series and Cisco TelePresence Video Communication Server (VCS) could allow an authenticated, remote attacker with read-write privileges on the application to perform a command injection attack that could result in remote code execution on an affected device.

 This vulnerability is due to insufficient validation of user-supplied input. An attacker could exploit this vulnerability by sending a crafted request to the web-based management interface of an affected device. A successful exploit could allow the attacker to establish a remote shell with root privileges.

Weakness: CWE-77 (Improper Neutralization of Special Elements used in a Command), CWE-94 (Improper Control of Generation of Code)

## Which versions are affected by CVE-2023-20209?

It affects 1 product.


Products: Cisco Telepresence Video Communication Server.

## How do I fix CVE-2023-20209?

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

## Is CVE-2023-20209 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2023-20209 exists.

Public exploit code:

- https://github.com/peter5he1by/CVE-2023-20209 (github_poc): https://github.com/peter5he1by/CVE-2023-20209

## Other vulnerabilities in Cisco TelePresence Video Communication Server (VCS) Expressway

- [CVE-2023-20105](https://insights.sbomify.com/CVE-2023-20105/): Privilege escalation in Cisco TelePresence Video Communication Server (VCS) Expressway (critical 9.6)
- [CVE-2023-20192](https://insights.sbomify.com/CVE-2023-20192/): Cisco Expressway Series and Cisco TelePresence Video Communication Server Privilege Escalation Vulnerabilities (critical 9.6)
- [CVE-2022-20754](https://insights.sbomify.com/CVE-2022-20754/): Cisco Expressway Series and Cisco TelePresence Video Communication Server Vulnerabilities (critical 9.0)
- [CVE-2022-20755](https://insights.sbomify.com/CVE-2022-20755/): Cisco Expressway Series and Cisco TelePresence Video Communication Server Vulnerabilities (critical 9.0)
- [CVE-2016-1468](https://insights.sbomify.com/CVE-2016-1468/): Command injection in n/a (high 8.8)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2023-20209 and fix it if it is affected.

What it is: CVE-2023-20209 is a medium-severity command injection vulnerability in Cisco TelePresence Video Communication Server (VCS) Expressway, published on 16 Aug 2023. An attacker needs administrator access to exploit it, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2023-20209 exists.

Affected product: Cisco TelePresence Video Communication Server (VCS) Expressway. 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-2023-20209/ (Markdown: https://insights.sbomify.com/CVE-2023-20209/index.md)
```

## Sources

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

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