# CVE-2016-1437: SQL injection in n/a

> Remote authenticated users can execute arbitrary SQL commands via crafted URLs in Cisco Prime Collaboration Deployment.

- **Severity:** Medium 6.5 (`CVSS:3.0/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 23 Jun 2016
- **Updated:** 5 Aug 2024
- **Also known as:** GHSA-4rmg-g9hw-8458

## What is CVE-2016-1437?

CVE-2016-1437 is a medium-severity SQL injection vulnerability in n/a, published on 23 Jun 2016. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

SQL injection vulnerability in the SQL database in Cisco Prime Collaboration Deployment before 11.5.1 allows remote authenticated users to execute arbitrary SQL commands via a crafted URL, aka Bug ID CSCuy92549.

Weakness: CWE-89 (Improper Neutralization of Special Elements used in an SQL Command)

## Which versions are affected by CVE-2016-1437?

It affects 1 product.


Products: Cisco Prime Collaboration Deployment.

## How do I fix CVE-2016-1437?

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

## Is CVE-2016-1437 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2023-20060](https://insights.sbomify.com/CVE-2023-20060/): Cisco Prime Collaboration Deployment Cross-Site Scripting Vulnerability (medium 6.1)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2016-1437 and fix it if it is affected.

What it is: CVE-2016-1437 is a medium-severity SQL injection vulnerability in n/a, published on 23 Jun 2016. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2016-1437 in the wild and no public exploit code.

Affected product: n/a. 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-2016-1437/ (Markdown: https://insights.sbomify.com/CVE-2016-1437/index.md)
```

## Sources

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

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