# CVE-2023-40282: Auth bypass in Rakuten WiFi Pocket

> A network-adjacent attacker can bypass authentication to access the management screen, allowing them to view sensitive information and modify settings.

- **Severity:** Medium 5.4 (`CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 23 Aug 2023
- **Updated:** 1 Jul 2025
- **Also known as:** GHSA-qrxh-6xj5-g3wh

## What is CVE-2023-40282?

CVE-2023-40282 is a medium-severity authentication bypass vulnerability in Rakuten WiFi Pocket, published on 23 Aug 2023. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

Improper authentication vulnerability in Rakuten WiFi Pocket all versions allows a network-adjacent attacker to log in to the product's Management Screen. As a result, sensitive information may be obtained and/or the settings may be changed.

Weakness: CWE-287 (Improper Authentication)

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

It affects 1 product.


Products: Rakuten Wifi Pocket Firmware.

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

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

## Is CVE-2023-40282 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2023-40282 is a medium-severity authentication bypass vulnerability in Rakuten WiFi Pocket, published on 23 Aug 2023. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2023-40282 in the wild and no public exploit code.

Affected product: Rakuten WiFi Pocket. 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-40282/ (Markdown: https://insights.sbomify.com/CVE-2023-40282/index.md)
```

## Sources

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

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