# CVE-2025-6751: Linksys E8450 HTTP POST Request portal.cgi set_device_language buffer overflow

> Remote attackers can trigger a buffer overflow in the Linksys E8450 router via a crafted HTTP POST request, potentially leading to code execution.

- **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:** 27 Jun 2025
- **Updated:** 27 Jun 2025
- **Also known as:** GHSA-6p5h-8mpm-mwqp

## What is CVE-2025-6751?

CVE-2025-6751 is a high-severity memory corruption vulnerability in Linksys E8450, published on 27 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, was found in Linksys E8450 up to 1.2.00.360516. This affects the function set_device_language of the file portal.cgi of the component HTTP POST Request Handler. The manipulation of the argument dut_language leads to buffer overflow. It is possible to initiate the attack remotely. The exploit has been disclosed to the public and may be used. The vendor was contacted early about this disclosure but did not respond in any way.

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

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


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

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

## Is CVE-2025-6751 being exploited?

There is no known exploitation of CVE-2025-6751 in the wild and no public exploit code.

## Fix prompt for AI coding agents

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

What it is: CVE-2025-6751 is a high-severity memory corruption vulnerability in Linksys E8450, published on 27 Jun 2025. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2025-6751 in the wild and no public exploit code.

Affected product: Linksys E8450. 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-6751/ (Markdown: https://insights.sbomify.com/CVE-2025-6751/index.md)
```

## Sources

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

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