# CVE-2025-71384: Memory corruption in n/a

> Administrators on the local network can execute OS commands via a stack-based buffer overflow in the DHCP comment field.

- **Severity:** Medium 6.7 (`CVSS:3.1/AV:L/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 6 Oct 2026
- **Updated:** 7 Oct 2026
- **Also known as:** GHSA-vgfm-pm37-pc7h

## What is CVE-2025-71384?

CVE-2025-71384 is a medium-severity memory corruption vulnerability in n/a, published on 6 Oct 2026. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

Dbit WIFI4 N300 1.0.0 devices allows administrators (from the local Wi-Fi network) to execute OS commands by leveraging a stack-based buffer overflow via the /api/addStaticDHCP comment field,

Weakness: CWE-121 (Stack-based Buffer Overflow)

## Which versions are affected by CVE-2025-71384?


## How do I fix CVE-2025-71384?

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

## Is CVE-2025-71384 being exploited?

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

Public exploit code:

- CVE-2025-71384 (github_poc): https://github.com/Scorpion-Security-Labs/CVE-2025-71384

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2025-71384 and fix it if it is affected.

What it is: CVE-2025-71384 is a medium-severity memory corruption vulnerability in n/a, published on 6 Oct 2026. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-71384 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-2025-71384/ (Markdown: https://insights.sbomify.com/CVE-2025-71384/index.md)
```

## Sources

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

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