# CVE-2022-45599: Auth bypass in n/a

> Attackers can gain escalated privileges on Aztech mesh routers via PHP type juggling in the login mechanism under specific password hash conditions.

- **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:** 22 Feb 2023
- **Updated:** 17 Mar 2025
- **Also known as:** GHSA-h44q-vvxg-q9wr

## What is CVE-2022-45599?

CVE-2022-45599 is a critical authentication bypass vulnerability in n/a, published on 22 Feb 2023. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Aztech WMB250AC Mesh Routers Firmware Version 016 2020 is vulnerable to PHP Type Juggling in file /var/www/login.php, allows attackers to gain escalated privileges only when specific conditions regarding a given accounts hashed password.

Weakness: CWE-522 (Insufficiently Protected Credentials)

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

It affects 1 product.


Products: Aztech Wmb250ac Firmware.

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

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

## Is CVE-2022-45599 being exploited?

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

Public exploit code:

- https://github.com/ethancunt/CVE-2022-45599 (github_poc): https://github.com/ethancunt/CVE-2022-45599

## Other vulnerabilities in n/a

- [CVE-2022-45600](https://insights.sbomify.com/CVE-2022-45600/): Command injection in n/a (high 8.8)

## Fix prompt for AI coding agents

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

What it is: CVE-2022-45599 is a critical authentication bypass vulnerability in n/a, published on 22 Feb 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-45599 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-45599/ (Markdown: https://insights.sbomify.com/CVE-2022-45599/index.md)
```

## Sources

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

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