# CVE-2022-45768: Command injection in n/a

> Attackers can execute arbitrary code on Edimax N300 routers via the formWlanMP function, posing a critical security risk.

- **Severity:** High 8.8 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 7 Feb 2023
- **Updated:** 25 Mar 2025
- **Also known as:** GHSA-39m8-rph8-x6gj

## What is CVE-2022-45768?

CVE-2022-45768 is a high-severity command injection vulnerability in n/a, published on 7 Feb 2023. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

Command Injection vulnerability in Edimax Technology Co., Ltd. Wireless Router N300 Firmware BR428nS v3 allows attacker to execute arbitrary code via the formWlanMP function.

Weakness: CWE-78 (Improper Neutralization of Special Elements used in an OS Command)

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

It affects 1 product.


Products: Edimax Br-6428ns Firmware.

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

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

## Is CVE-2022-45768 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2023-31986](https://insights.sbomify.com/CVE-2023-31986/): Command injection in n/a (critical 9.8)
- [CVE-2023-31983](https://insights.sbomify.com/CVE-2023-31983/): Command injection in n/a (critical 9.8)
- [CVE-2023-31985](https://insights.sbomify.com/CVE-2023-31985/): Command injection in n/a (critical 9.8)

## Fix prompt for AI coding agents

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

What it is: CVE-2022-45768 is a high-severity command injection vulnerability in n/a, published on 7 Feb 2023. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2022-45768 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-2022-45768/ (Markdown: https://insights.sbomify.com/CVE-2022-45768/index.md)
```

## Sources

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

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