# CVE-2016-2281: Privilege escalation in n/a

> Local attackers can gain privileges by placing a malicious DLL in the working directory of ABB Panel Builder 800.

- **Severity:** High 7.2 (`CVSS:3.0/AV:L/AC:H/PR:H/UI:R/S:C/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Local or same network only
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 18 Mar 2016
- **Updated:** 5 Aug 2024
- **Also known as:** GHSA-3gr5-qjr2-qff6

## What is CVE-2016-2281?

CVE-2016-2281 is a high-severity vulnerability in n/a, published on 18 Mar 2016. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.

### Official description

Untrusted search path vulnerability in ABB Panel Builder 800 5.1 allows local users to gain privileges via a Trojan horse DLL in the current working directory.

Weakness: CWE-264

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

It affects 1 product.


Products: Abb Panel Builder 800.

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

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

## Is CVE-2016-2281 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2018-10616](https://insights.sbomify.com/CVE-2018-10616/): Code injection in ABB Panel Builder 800 (high 7.8)

## Fix prompt for AI coding agents

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

What it is: CVE-2016-2281 is a high-severity vulnerability in n/a, published on 18 Mar 2016. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2016-2281 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-2281/ (Markdown: https://insights.sbomify.com/CVE-2016-2281/index.md)
```

## Sources

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

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