# CVE-2016-8921: File upload in FileNet Content Manager

> Remote attackers can upload arbitrary files to IBM FileNet Content Manager, leading to arbitrary code execution on the server.

- **Severity:** High 8.8 (`CVSS:3.0/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H`)
- **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:** 1 Feb 2017
- **Updated:** 6 Aug 2024
- **Also known as:** GHSA-388v-hgcc-fmvm

## What is CVE-2016-8921?

CVE-2016-8921 is a high-severity vulnerability in IBM Corporation FileNet Content Manager, published on 1 Feb 2017. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

IBM FileNet WorkPlace XT could allow a remote attacker to upload arbitrary files, which could allow the attacker to execute arbitrary code on the vulnerable server.

Weakness: CWE-434 (Unrestricted Upload of File with Dangerous Type)

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

It affects 1 product.


Products: Ibm Filenet Workplace Xt.

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

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

## Is CVE-2016-8921 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2016-8921 is a high-severity vulnerability in IBM Corporation FileNet Content Manager, published on 1 Feb 2017. 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-8921 in the wild and no public exploit code.

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

## Sources

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

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