# CVE-2022-38627: SQL injection in n/a

> Attackers can exploit SQL injection in the Linear eMerge E3-Series access control system to read or modify database contents.

- **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:** 3 Jan 2023
- **Updated:** 10 Apr 2025
- **Also known as:** GHSA-874w-6q69-xqm4

## What is CVE-2022-38627?

CVE-2022-38627 is a critical SQL injection vulnerability in n/a, published on 3 Jan 2023. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Nortek Linear eMerge E3-Series 0.32-08f, 0.32-07p, 0.32-07e, 0.32-09c, 0.32-09b, 0.32-09a, and 0.32-08e were discovered to contain a SQL injection vulnerability via the idt parameter.

Weakness: CWE-89 (Improper Neutralization of Special Elements used in an SQL Command)

## Which versions are affected by CVE-2022-38627?

It affects 1 product.


Products: Niceforyou Linear Emerge E3 Access Control Firmware.

## How do I fix CVE-2022-38627?

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

## Is CVE-2022-38627 being exploited?

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

Public exploit code:

- Nortek Linear eMerge E3-Series - SQL Injection (nuclei): http/cves/2022/CVE-2022-38627.yaml

## Other vulnerabilities in n/a

- [CVE-2022-38628](https://insights.sbomify.com/CVE-2022-38628/): Cross-site scripting in n/a (medium 6.1)
- [CVE-2022-46381](https://insights.sbomify.com/CVE-2022-46381/): Cross-site scripting in n/a (medium 6.1)
- [CVE-2022-42710](https://insights.sbomify.com/CVE-2022-42710/): Cross-site scripting in n/a (medium 5.4)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2022-38627 and fix it if it is affected.

What it is: CVE-2022-38627 is a critical SQL injection vulnerability in n/a, published on 3 Jan 2023. 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-2022-38627 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-2022-38627/ (Markdown: https://insights.sbomify.com/CVE-2022-38627/index.md)
```

## Sources

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

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