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

> Attackers can bypass access controls and gain complete application access by modifying an HTTP header in Multilaser Wi-Fi extenders.

- **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:** 5 Mar 2024
- **Updated:** 4 Nov 2025
- **Also known as:** GHSA-wxc9-fjcg-2chx

## What is CVE-2023-38944?

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

### Official description

An issue in Multilaser RE160V firmware v12.03.01.09_pt and Multilaser RE163V firmware v12.03.01.10_pt allows attackers to bypass the access control and gain complete access to the application via modifying a HTTP header.

Weakness: CWE-269 (Improper Privilege Management)

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

It affects 2 products.


Products: Multilaser Re160v Firmware, Multilaser Re163v Firmware.

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

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

## Is CVE-2023-38944 being exploited?

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

## Fix prompt for AI coding agents

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

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

## Sources

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

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