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

> Attackers can bypass authentication on the HNAP1 interface to log in as administrator with empty passwords, gaining full control of the router.

- **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:** 11 Jan 2024
- **Updated:** 20 Jun 2025
- **Also known as:** GHSA-jwhp-365f-27vv

## What is CVE-2023-51987?

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

### Official description

D-Link DIR-822+ V1.0.2 contains a login bypass in the HNAP1 interface, which allows attackers to log in to administrator accounts with empty passwords.

Weakness: CWE-306 (Missing Authentication for Critical Functionality)

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

It affects 1 product.


Products: Dlink Dir-822 Firmware.

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

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

## Is CVE-2023-51987 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2023-51984](https://insights.sbomify.com/CVE-2023-51984/): Command injection in n/a (critical 9.8)
- [CVE-2026-7067](https://insights.sbomify.com/CVE-2026-7067/): D-Link DIR-822 udhcpd DHCP Service dhcpd.c system command injection (medium 6.9)

## Fix prompt for AI coding agents

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

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

## Sources

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

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