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

> Attackers can bypass NGINX authentication on GL.iNet routers via Lua string pattern matching flaws, gaining unauthorized access.

- **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:** 12 Jan 2024
- **Updated:** 3 Jun 2025
- **Also known as:** GHSA-3vmx-5x6r-25cw

## What is CVE-2023-50919?

CVE-2023-50919 is a critical authentication bypass vulnerability in n/a, published on 12 Jan 2024. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

An issue was discovered on GL.iNet devices before version 4.5.0. There is an NGINX authentication bypass via Lua string pattern matching. This affects A1300 4.4.6, AX1800 4.4.6, AXT1800 4.4.6, MT3000 4.4.6, MT2500 4.4.6, MT6000 4.5.0, MT1300 4.3.7, MT300N-V2 4.3.7, AR750S 4.3.7, AR750 4.3.7, AR300M 4.3.7, and B1300 4.3.7.

Weakness: CWE-287 (Improper Authentication)

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

It affects 12 products.


Products: Gl-Inet Gl-A1300 Firmware, Gl-Inet Gl-Ar300m Firmware, Gl-Inet Gl-Ar750 Firmware, Gl-Inet Gl-Ar750s Firmware, Gl-Inet Gl-Ax1800 Firmware, Gl-Inet Gl-Axt1800 Firmware, Gl-Inet Gl-B1300 Firmware, Gl-Inet Gl-Mt1300 Firmware, Gl-Inet Gl-Mt2500 Firmware, Gl-Inet Gl-Mt3000 Firmware, Gl-Inet Gl-Mt300n-V2 Firmware, Gl-Inet Gl-Mt6000 Firmware.

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

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

## Is CVE-2023-50919 being exploited?

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

Public exploit code:

- GL.iNet Unauthenticated Remote Command Execution via the logread module. (metasploit)

## Other vulnerabilities in n/a

- [CVE-2023-50921](https://insights.sbomify.com/CVE-2023-50921/): Privilege escalation in n/a (critical 9.8)
- [CVE-2023-31471](https://insights.sbomify.com/CVE-2023-31471/): Security feature bypass in n/a (critical 9.8)
- [CVE-2023-31475](https://insights.sbomify.com/CVE-2023-31475/): Memory corruption in n/a (critical 9.0)
- [CVE-2023-50445](https://insights.sbomify.com/CVE-2023-50445/): Command injection in n/a (high 7.8)
- [CVE-2023-31477](https://insights.sbomify.com/CVE-2023-31477/): Path traversal in n/a (high 7.5)

## Fix prompt for AI coding agents

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

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

## Sources

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

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