# CVE-2025-8168: D-Link DIR-513 formSetWanPPPoE websAspInit buffer overflow

> Remote attackers can exploit a buffer overflow in the PPPoE configuration interface of unsupported D-Link DIR-513 routers to execute arbitrary code.

- **Severity:** High 8.7 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N/E:P`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 25 Jul 2025
- **Updated:** 25 Jul 2025
- **Also known as:** GHSA-gp8p-9xfx-q8f8

## What is CVE-2025-8168?

CVE-2025-8168 is a high-severity memory corruption vulnerability in D-Link DIR-513, published on 25 Jul 2025. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

A vulnerability was found in D-Link DIR-513 1.10. It has been rated as critical. Affected by this issue is the function websAspInit of the file /goform/formSetWanPPPoE. The manipulation of the argument curTime leads to buffer overflow. The attack may be launched remotely. The exploit has been disclosed to the public and may be used. This vulnerability only affects products that are no longer supported by the maintainer.

Weakness: CWE-120 (Buffer Copy without Checking Size of Input), CWE-787 (Out-of-bounds Write), CWE-119 (Improper Restriction of Operations within the Bounds of a Memory Buffer)

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

It affects 1 product.


Products: Dlink Dir-513 Firmware.

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

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

## Is CVE-2025-8168 being exploited?

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

## Other vulnerabilities in D-Link DIR-513

- [CVE-2025-70229](https://insights.sbomify.com/CVE-2025-70229/): Memory corruption in n/a (critical 9.8)
- [CVE-2025-70230](https://insights.sbomify.com/CVE-2025-70230/): Memory corruption in n/a (critical 9.8)
- [CVE-2025-70231](https://insights.sbomify.com/CVE-2025-70231/): Path traversal in n/a (critical 9.8)
- [CVE-2025-70232](https://insights.sbomify.com/CVE-2025-70232/): Memory corruption in n/a (critical 9.8)
- [CVE-2025-70233](https://insights.sbomify.com/CVE-2025-70233/): Memory corruption in n/a (critical 9.8)

## Fix prompt for AI coding agents

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

What it is: CVE-2025-8168 is a high-severity memory corruption vulnerability in D-Link DIR-513, published on 25 Jul 2025. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-8168 exists.

Affected product: D-Link DIR-513. 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-8168/ (Markdown: https://insights.sbomify.com/CVE-2025-8168/index.md)
```

## Sources

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

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