# CVE-2025-5408: WAVLINK WL-WN576K1 HTTP POST Request login.cgi sys_login buffer overflow

> Remote attackers can trigger a buffer overflow in the login handler of WAVLINK routers, potentially leading to code execution or service disruption.

- **Severity:** Critical 9.3 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 1 Jun 2025
- **Updated:** 2 Jun 2025
- **Also known as:** GHSA-hwq5-562f-8695

## What is CVE-2025-5408?

CVE-2025-5408 is a critical memory corruption vulnerability in WAVLINK QUANTUM D2G, published on 1 Jun 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

A vulnerability was found in WAVLINK QUANTUM D2G, QUANTUM D3G, WL-WN530G3A, WL-WN530HG3, WL-WN532A3 and WL-WN576K1 up to V1410_240222 and classified as critical. Affected by this issue is the function sys_login of the file /cgi-bin/login.cgi of the component HTTP POST Request Handler. The manipulation of the argument login_page leads to buffer overflow. The attack may be launched 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-5408?


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

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

## Is CVE-2025-5408 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2025-5408 is a critical memory corruption vulnerability in WAVLINK QUANTUM D2G, published on 1 Jun 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2025-5408 in the wild and no public exploit code.

Affected product: WAVLINK QUANTUM D2G. 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-5408/ (Markdown: https://insights.sbomify.com/CVE-2025-5408/index.md)
```

## Sources

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

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