# CVE-2021-37292: Hardcoded credentials in n/a

> An undocumented backdoor account with admin privileges allows attackers to gain full system control of the Building Energy Management System.

- **Severity:** High 7.2 (`CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 11 Apr 2022
- **Updated:** 5 Jul 2026
- **Also known as:** GHSA-xhgx-qjr6-8ff6

## What is CVE-2021-37292?

CVE-2021-37292 is a high-severity vulnerability in n/a, published on 11 Apr 2022. An attacker needs administrator access to exploit it, with no action from the victim.

### Official description

An Access Control vulnerability exists in KevinLAB Inc Building Energy Management System 4ST BEMS 1.0.0 due to an undocumented backdoor account. A malicious user can log in using the backdor account with admin highest privileges and obtain system control.

## Which versions are affected by CVE-2021-37292?

It affects 1 product.


Products: Kevinlab 4st L-Bems.

## How do I fix CVE-2021-37292?

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

## Is CVE-2021-37292 being exploited?

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

Public exploit code:

- KevinLAB BEMS (Building Energy Management System) - Backdoor Account (nuclei): http/cves/2021/CVE-2021-37292.yaml

## Other vulnerabilities in n/a

- [CVE-2021-37291](https://insights.sbomify.com/CVE-2021-37291/): SQL injection in n/a (critical 9.8)
- [CVE-2021-37293](https://insights.sbomify.com/CVE-2021-37293/): Path traversal in n/a (medium 6.5)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2021-37292 and fix it if it is affected.

What it is: CVE-2021-37292 is a high-severity vulnerability in n/a, published on 11 Apr 2022. An attacker needs administrator access to exploit it, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2021-37292 exists.

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-2021-37292/ (Markdown: https://insights.sbomify.com/CVE-2021-37292/index.md)
```

## Sources

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

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