# CVE-2019-1915: Multiple Cisco Unified Communications Products Cross-Site Request Forgery Vulnerability

> An attacker can trick users into clicking a link to change their passwords, allowing unauthorized actions on behalf of the victim.

- **Severity:** Medium 6.5 (`CVSS:3.0/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:H/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-9p4j-gv3h-8q29

## What is CVE-2019-1915?

CVE-2019-1915 is a medium-severity vulnerability in Cisco Unified Communications Manager, 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 the web-based interface of Cisco Unified Communications Manager, Cisco Unified Communications Manager Session Management Edition (SME), Cisco Unified Communications Manager IM and Presence (Unified CM IM&P) Service, and Cisco Unity Connection could allow an unauthenticated, remote attacker to conduct a cross-site request forgery (CSRF) attack on an affected system. The vulnerability is due to insufficient CSRF protections by the affected software. An attacker could exploit this vulnerability by persuading a targeted user to click a malicious link. A successful exploit could allow the attacker to send arbitrary requests that could change the password of a targeted user. An attacker could then take unauthorized actions on behalf of the targeted user.

Weakness: CWE-352 (Cross-Site Request Forgery)

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

It affects 3 products.


Products: Cisco Unified Communications Manager, Cisco Unified Communications Manager Im and Presence Service, Cisco Unity Connection.

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

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

## Is CVE-2019-1915 being exploited?

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

## Other vulnerabilities in Cisco Unified Communications Manager

- [CVE-2026-20230](https://insights.sbomify.com/CVE-2026-20230/): Cisco Unified Communications Manager Server-Side Request Forgery (SSRF) (high 8.6, exploited in the wild)
- [CVE-2026-20045](https://insights.sbomify.com/CVE-2026-20045/): Cisco Unified Communications Products Code Injection (high 8.2, exploited in the wild)
- [CVE-2025-20309](https://insights.sbomify.com/CVE-2025-20309/): Cisco Unified Communications Manager Static SSH Credentials Vulnerability (critical 10.0)
- [CVE-2011-1643](https://insights.sbomify.com/CVE-2011-1643/): Information disclosure in n/a (critical 10.0)
- [CVE-2024-20253](https://insights.sbomify.com/CVE-2024-20253/): Deserialization in Cisco Packaged Contact Center Enterprise (critical 9.9)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2019-1915 and fix it if it is affected.

What it is: CVE-2019-1915 is a medium-severity vulnerability in Cisco Unified Communications Manager, 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-1915 in the wild and no public exploit code.

Affected product: Cisco Unified Communications Manager. 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-1915/ (Markdown: https://insights.sbomify.com/CVE-2019-1915/index.md)
```

## Sources

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

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