# CVE-2022-43553: Privilege escalation in EdgeMAX EdgeRouter

> An operator can escalate privileges to execute arbitrary administrator commands on EdgeRouters, requiring an upgrade to the latest firmware.

- **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:** 5 Dec 2022
- **Updated:** 24 Apr 2025
- **Also known as:** GHSA-82vg-p6h3-hr69

## What is CVE-2022-43553?

CVE-2022-43553 is a high-severity vulnerability in EdgeMAX EdgeRouter, published on 5 Dec 2022. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

A remote code execution vulnerability in EdgeRouters (Version 2.0.9-hotfix.4 and earlier) allows a malicious actor with an operator account to run arbitrary administrator commands.This vulnerability is fixed in Version 2.0.9-hotfix.5 and later.

Weakness: CWE-250 (Execution with Unnecessary Privileges)

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

It affects 1 product.


Products: Ui Edgemax Edgerouter Firmware.

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

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

## Is CVE-2022-43553 being exploited?

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

## Other vulnerabilities in EdgeMAX EdgeRouter

- [CVE-2023-2373](https://insights.sbomify.com/CVE-2023-2373/): Ubiquiti EdgeRouter X Web Management command injection (high 8.6)
- [CVE-2021-22909](https://insights.sbomify.com/CVE-2021-22909/): Other in EdgeMAX EdgeRouter (high 7.5)

## Fix prompt for AI coding agents

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

What it is: CVE-2022-43553 is a high-severity vulnerability in EdgeMAX EdgeRouter, published on 5 Dec 2022. 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-43553 in the wild and no public exploit code.

Affected product: EdgeMAX EdgeRouter. 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-43553/ (Markdown: https://insights.sbomify.com/CVE-2022-43553/index.md)
```

## Sources

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

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