# CVE-2018-16161: Privilege escalation in OpenDolphin

> Authenticated users can escalate privileges to administrative level in OpenDolphin, allowing them to perform unintended operations.

- **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:** 15 Nov 2018
- **Updated:** 5 Aug 2024
- **Also known as:** GHSA-97hp-cm4g-33xq

## What is CVE-2018-16161?

CVE-2018-16161 is a high-severity vulnerability in Life Sciences Computing Corporation OpenDolphin, published on 15 Nov 2018. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

OpenDolphin 2.7.0 and earlier allows authenticated users to gain administrative privileges and perform unintended operations.

## Which versions are affected by CVE-2018-16161?

It affects 1 product.


Products: Opendolphin Opendolphin.

## How do I fix CVE-2018-16161?

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

## Is CVE-2018-16161 being exploited?

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

## Other vulnerabilities in Life Sciences Computing Corporation OpenDolphin

- [CVE-2018-16162](https://insights.sbomify.com/CVE-2018-16162/): Information disclosure in OpenDolphin (high 8.8)
- [CVE-2018-16163](https://insights.sbomify.com/CVE-2018-16163/): Auth bypass in OpenDolphin (medium 6.5)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2018-16161 and fix it if it is affected.

What it is: CVE-2018-16161 is a high-severity vulnerability in Life Sciences Computing Corporation OpenDolphin, published on 15 Nov 2018. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2018-16161 in the wild and no public exploit code.

Affected product: Life Sciences Computing Corporation OpenDolphin. 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-2018-16161/ (Markdown: https://insights.sbomify.com/CVE-2018-16161/index.md)
```

## Sources

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

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