# CVE-2016-5889: Cross-site request forgery in Interact

> Attackers can trick authenticated users into performing unauthorized actions in IBM Interact via cross-site request forgery.

- **Severity:** High 8.8 (`CVSS:3.0/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H`)
- **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:** 10 May 2017
- **Updated:** 6 Aug 2024
- **Also known as:** GHSA-pwgf-m63g-p84j

## What is CVE-2016-5889?

CVE-2016-5889 is a high-severity vulnerability in IBM Corporation Interact, published on 10 May 2017. 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

IBM Interact 8.6, 9.0, 9.1, and 10.0 is vulnerable to cross-site request forgery which could allow an attacker to execute malicious and unauthorized actions transmitted from a user that the website trusts. IBM X-Force ID: 115085.

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

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

It affects 1 product.


Products: Ibm Interact.

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

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

## Is CVE-2016-5889 being exploited?

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

## Other vulnerabilities in IBM Corporation Interact

- [CVE-2016-5888](https://insights.sbomify.com/CVE-2016-5888/): Cross-site scripting in Interact (medium 5.4)

## Fix prompt for AI coding agents

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

What it is: CVE-2016-5889 is a high-severity vulnerability in IBM Corporation Interact, published on 10 May 2017. 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-2016-5889 in the wild and no public exploit code.

Affected product: IBM Corporation Interact. 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-5889/ (Markdown: https://insights.sbomify.com/CVE-2016-5889/index.md)
```

## Sources

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

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