# CVE-2025-20277: Cisco Unified Contact Center Express Path Traversal Vulnerability

> An authenticated local attacker can exploit path traversal in Cisco Unified CCX to execute arbitrary code and potentially escalate privileges to root.

- **Severity:** Low 3.4 (`CVSS:3.1/AV:L/AC:L/PR:H/UI:N/S:U/C:L/I:L/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 4 Jun 2025
- **Updated:** 26 Feb 2026
- **Also known as:** GHSA-6j7v-2g8q-wx49

## What is CVE-2025-20277?

CVE-2025-20277 is a low-severity path traversal vulnerability in Cisco Unified Contact Center Express, published on 4 Jun 2025. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

A vulnerability in the web-based management interface of Cisco Unified CCX could allow an authenticated, local attacker to execute arbitrary code on an affected device. To exploit this vulnerability, the attacker must have valid administrative credentials.

This vulnerability is due to improper limitation of a pathname to a restricted directory (path traversal). An attacker could exploit this vulnerability by sending a crafted web request to an affected device, followed by a specific command through an SSH session. A successful exploit could allow the attacker to execute arbitrary code on the underlying operating system of an affected device as a low-privilege user. A successful exploit could also allow the attacker to undertake further actions to elevate their privileges to root.

Weakness: CWE-22 (Improper Limitation of a Pathname to a Restricted Directory)

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

It affects 1 product.


Products: Cisco Unified Contact Center Express.

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

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

## Is CVE-2025-20277 being exploited?

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

## Other vulnerabilities in Cisco Unified Contact Center Express

- [CVE-2025-20354](https://insights.sbomify.com/CVE-2025-20354/): Cisco Unified Contact Center Express Remote Code Execution Vulnerability (critical 9.8)
- [CVE-2020-3280](https://insights.sbomify.com/CVE-2020-3280/): Cisco Unified Contact Center Express Remote Code Execution Vulnerability (critical 9.8)
- [CVE-2018-0403](https://insights.sbomify.com/CVE-2018-0403/): Information disclosure in Cisco Unified Contact Center Express unknown (critical 9.8)
- [CVE-2022-20658](https://insights.sbomify.com/CVE-2022-20658/): Privilege escalation in Cisco Unified Contact Center Domain Manager (critical 9.6)
- [CVE-2025-20358](https://insights.sbomify.com/CVE-2025-20358/): Cisco Unified Contact Center Express Editor Authentication Bypass Vulnerability (critical 9.4)

## Fix prompt for AI coding agents

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

What it is: CVE-2025-20277 is a low-severity path traversal vulnerability in Cisco Unified Contact Center Express, published on 4 Jun 2025. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2025-20277 in the wild and no public exploit code.

Affected product: Cisco Unified Contact Center Express. 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-20277/ (Markdown: https://insights.sbomify.com/CVE-2025-20277/index.md)
```

## Sources

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

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