# CVE-2025-6614: D-Link DIR-619L formSetWANType_Wizard5 stack-based overflow

> Remote attackers can execute arbitrary code via a stack-based buffer overflow in the WAN configuration interface of unsupported D-Link routers.

- **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 Jun 2025
- **Updated:** 26 Jun 2025
- **Also known as:** GHSA-3266-jrw3-w36w

## What is CVE-2025-6614?

CVE-2025-6614 is a high-severity memory corruption vulnerability in Dlink Dir-619l Firmware, published on 25 Jun 2025. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

A vulnerability, which was classified as critical, has been found in D-Link DIR-619L 2.06B01. Affected by this issue is the function formSetWANType_Wizard5 of the file /goform/formSetWANType_Wizard5. The manipulation of the argument curTime leads to stack-based 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-121 (Stack-based Buffer Overflow), CWE-119 (Improper Restriction of Operations within the Bounds of a Memory Buffer)

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

It affects 1 product.


Products: Dlink Dir-619l Firmware.

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

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

## Is CVE-2025-6614 being exploited?

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

## Other vulnerabilities in Dlink Dir-619l Firmware

- [CVE-2025-55599](https://insights.sbomify.com/CVE-2025-55599/): Memory corruption in n/a (critical 9.8)
- [CVE-2025-55602](https://insights.sbomify.com/CVE-2025-55602/): Memory corruption in n/a (critical 9.8)
- [CVE-2025-55611](https://insights.sbomify.com/CVE-2025-55611/): Memory corruption in n/a (critical 9.8)
- [CVE-2023-43869](https://insights.sbomify.com/CVE-2023-43869/): Memory corruption in n/a (critical 9.8)
- [CVE-2020-19319](https://insights.sbomify.com/CVE-2020-19319/): Memory corruption in n/a (critical 9.8)

## Fix prompt for AI coding agents

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

What it is: CVE-2025-6614 is a high-severity memory corruption vulnerability in Dlink Dir-619l Firmware, published on 25 Jun 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-6614 exists.

Affected product: Dlink Dir-619l Firmware. 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-6614/ (Markdown: https://insights.sbomify.com/CVE-2025-6614/index.md)
```

## Sources

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

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