# CVE-2023-47716: IBM FileNet Content Manager privilege escalation

> A user can gain the privileges of another user in IBM FileNet Content Manager under unusual circumstances, requiring a patch.

- **Severity:** Medium 6.3 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:L`)
- **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 Mar 2024
- **Updated:** 20 Sep 2024
- **Also known as:** GHSA-9whp-qh87-g9m8

## What is CVE-2023-47716?

CVE-2023-47716 is a medium-severity vulnerability in IBM Filenet Content Manager, published on 1 Mar 2024. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

IBM CP4BA - Filenet Content Manager Component 5.5.8.0, 5.5.10.0, and 5.5.11.0 could allow a user to gain the privileges of another user under unusual circumstances.  IBM X-Force ID:  271656.

Weakness: CWE-863 (Incorrect Authorization)

## Which versions are affected by CVE-2023-47716?

It affects 2 products.


Products: Ibm Cp4ba - Filenet Content Manager, Ibm Filenet Content Manager.

## How do I fix CVE-2023-47716?

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

## Is CVE-2023-47716 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2023-47716 and fix it if it is affected.

What it is: CVE-2023-47716 is a medium-severity vulnerability in IBM Filenet Content Manager, published on 1 Mar 2024. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2023-47716 in the wild and no public exploit code.

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

## Sources

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

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