# CVE-2019-7261: Hardcoded credentials in n/a

> Attackers can use hard-coded credentials to gain unauthorized access to Linear eMerge E3-Series devices.

- **Severity:** Critical 9.8 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/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:** Not needed
- **Fix available:** No
- **Published:** 2 Jul 2019
- **Updated:** 4 Aug 2024
- **Also known as:** GHSA-8jgq-23x7-86xm

## What is CVE-2019-7261?

CVE-2019-7261 is a critical vulnerability in n/a, published on 2 Jul 2019. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Linear eMerge E3-Series devices have Hard-coded Credentials.

Weakness: CWE-798 (Use of Hard-coded Credentials)

## Which versions are affected by CVE-2019-7261?

It affects 2 products.


Products: Nortekcontrol Linear Emerge Elite Firmware, Nortekcontrol Linear Emerge Essential Firmware.

## How do I fix CVE-2019-7261?

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

## Is CVE-2019-7261 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2019-7256](https://insights.sbomify.com/CVE-2019-7256/): Nice Linear eMerge E3-Series OS Command Injection (critical 9.8, exploited in the wild)
- [CVE-2019-7257](https://insights.sbomify.com/CVE-2019-7257/): File upload in n/a (critical 10.0)
- [CVE-2019-7252](https://insights.sbomify.com/CVE-2019-7252/): Hardcoded credentials in n/a (critical 9.8)
- [CVE-2019-7253](https://insights.sbomify.com/CVE-2019-7253/): Path traversal in n/a (critical 9.8)
- [CVE-2019-7260](https://insights.sbomify.com/CVE-2019-7260/): Hardcoded credentials in n/a (critical 9.8)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2019-7261 and fix it if it is affected.

What it is: CVE-2019-7261 is a critical vulnerability in n/a, published on 2 Jul 2019. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2019-7261 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-2019-7261/ (Markdown: https://insights.sbomify.com/CVE-2019-7261/index.md)
```

## Sources

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

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