# CVE-2019-15259: Cisco Unified Contact Center Express HTTP Response Splitting Vulnerability

> Unauthenticated attackers can exploit HTTP response splitting in Cisco UCCX to perform cross-site scripting and cache poisoning attacks.

- **Severity:** Medium 6.1 (`CVSS:3.0/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:** 2 Oct 2019
- **Updated:** 21 Nov 2024
- **Also known as:** GHSA-cmh5-cf9g-7v34

## What is CVE-2019-15259?

CVE-2019-15259 is a medium-severity cross-site scripting vulnerability in Cisco Unified Contact Center Express, published on 2 Oct 2019. 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 Unified Contact Center Express (UCCX) Software could allow an unauthenticated, remote attacker to conduct an HTTP response splitting attack. The vulnerability is due to insufficient input validation of some parameters that are passed to the web server of the affected system. An attacker could exploit this vulnerability by convincing a user to follow a malicious link or by intercepting a user request on an affected device. A successful exploit could allow the attacker to perform cross-site scripting attacks, web cache poisoning, access sensitive browser-based information, and similar exploits.

Weakness: CWE-74 (Improper Neutralization of Special Elements in Output Used by a Downstream Component), CWE-113 (Improper Neutralization of CRLF Sequences in HTTP Headers)

## Which versions are affected by CVE-2019-15259?

It affects 1 product.


Products: Cisco Unified Contact Center Express.

## How do I fix CVE-2019-15259?

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

## Is CVE-2019-15259 being exploited?

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

What it is: CVE-2019-15259 is a medium-severity cross-site scripting vulnerability in Cisco Unified Contact Center Express, published on 2 Oct 2019. 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-2019-15259 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-2019-15259/ (Markdown: https://insights.sbomify.com/CVE-2019-15259/index.md)
```

## Sources

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

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