# CVE-2023-28760: Memory corruption in n/a

> Unauthenticated LAN attackers can execute arbitrary code as root via a stack-based buffer overflow in minidlnad when a USB drive is connected.

- **Severity:** High 7.5 (`CVSS:3.1/AV:A/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H`)
- **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:** 2 Oct 2025
- **Updated:** 2 Oct 2025
- **Also known as:** GHSA-h87w-qr7h-rc63

## What is CVE-2023-28760?

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

### Official description

TP-Link AX1800 WiFi 6 Router (Archer AX21) devices allow unauthenticated attackers (on the LAN) to execute arbitrary code as root via the db_dir field to minidlnad. The attacker obtains the ability to modify files.db, and that can be used to reach a stack-based buffer overflow in minidlna-1.1.2/upnpsoap.c. Exploitation requires that a USB flash drive is connected to the router (customers often do this to make a \\192.168.0.1 share available on their local network).

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

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


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

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

## Is CVE-2023-28760 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2023-28760 is a high-severity memory corruption vulnerability in n/a, published on 2 Oct 2025. 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-2023-28760 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-28760/ (Markdown: https://insights.sbomify.com/CVE-2023-28760/index.md)
```

## Sources

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

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