# CVE-2023-46453: Auth bypass in n/a

> Attackers can bypass authentication on GL.iNet routers using crafted SQL/regex usernames to gain administrative control.

- **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:** 8 May 2026
- **Updated:** 8 May 2026
- **Also known as:** GHSA-vx26-r59q-724x

## What is CVE-2023-46453?

CVE-2023-46453 is a critical authentication bypass vulnerability in n/a, published on 8 May 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Certain GL.iNet devices with 4.x firmware allow authentication bypass (resulting in administrative control of the device) via a username that is both a valid SQL statement and a valid regular expression. For example, this affects version 4.3.7 on GL-MT3000 GL-AR300M GL-B1300 GL-AX1800 GL-AR750S GL-MT2500 GL-AXT1800 GL-X3000 and GL-SFT1200.

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

## Which versions are affected by CVE-2023-46453?


## How do I fix CVE-2023-46453?

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

## Is CVE-2023-46453 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2023-46453 and fix it if it is affected.

What it is: CVE-2023-46453 is a critical authentication bypass vulnerability in n/a, published on 8 May 2026. 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-2023-46453 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-2023-46453/ (Markdown: https://insights.sbomify.com/CVE-2023-46453/index.md)
```

## Sources

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

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