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

> A stack buffer overflow in D-Link DIR-513 routers allows attackers to execute arbitrary code or cause denial of service via the webPage parameter.

- **Severity:** High 7.5 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/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:** 10 Mar 2026
- **Updated:** 10 Mar 2026
- **Also known as:** GHSA-269q-2cg6-vx42

## What is CVE-2025-70242?

CVE-2025-70242 is a high-severity memory corruption vulnerability in n/a, published on 10 Mar 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Stack buffer overflow vulnerability in D-Link DIR-513 v1.10 via the webPage parameter to goform/formSetWanPPTP.

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

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

It affects 1 product.


Products: Dlink Dir-513 Firmware.

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

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

## Is CVE-2025-70242 being exploited?

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

## Other vulnerabilities in n/a

- [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-70242 and fix it if it is affected.

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

## Sources

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

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