# CVE-2020-37092: Netis E1+ 1.2.32533 - Backdoor Account (root)

> Unauthenticated attackers can use hardcoded root credentials to gain full administrative access to the Netis E1+ router.

- **Severity:** Critical 9.3 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 3 Feb 2026
- **Updated:** 4 Feb 2026
- **Also known as:** GHSA-mr9h-r8jv-mpqc

## What is CVE-2020-37092?

CVE-2020-37092 is a critical vulnerability in Netis E1+, published on 3 Feb 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Netis E1+ version 1.2.32533 contains a hardcoded root account vulnerability that allows unauthenticated attackers to access the device with predefined credentials. Attackers can leverage the embedded root account with a crackable password to gain full administrative access to the network device.

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

## Which versions are affected by CVE-2020-37092?


## How do I fix CVE-2020-37092?

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

## Is CVE-2020-37092 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2020-37092 exists.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2020-37092 and fix it if it is affected.

What it is: CVE-2020-37092 is a critical vulnerability in Netis E1+, published on 3 Feb 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2020-37092 exists.

Affected product: Netis E1+. 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-2020-37092/ (Markdown: https://insights.sbomify.com/CVE-2020-37092/index.md)
```

## Sources

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

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