# CVE-2025-10322: Wavlink WL-WN578W2 sysinit.html password recovery

> Remote attackers can bypass password recovery mechanisms on Wavlink WL-WN578W2 routers to gain unauthorized administrative access.

- **Severity:** Medium 6.9 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:L/VA:N/SC:N/SI:N/SA:N/E:P`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 12 Sep 2025
- **Updated:** 12 Sep 2025
- **Also known as:** GHSA-9473-jhhc-4cq3

## What is CVE-2025-10322?

CVE-2025-10322 is a medium-severity vulnerability in Wavlink WL-WN578W2, published on 12 Sep 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

A vulnerability has been found in Wavlink WL-WN578W2 221110. The affected element is an unknown function of the file /sysinit.html. The manipulation of the argument newpass/confpass leads to weak password recovery. The attack is possible to be carried out 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-640 (Weak Password Recovery Mechanism for Forgotten Password)

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

It affects 1 product.


Products: Wavlink Wl-Wn578w2 Firmware.

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

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

## Is CVE-2025-10322 being exploited?

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

## Other vulnerabilities in Wavlink WL-WN578W2

- [CVE-2025-10358](https://insights.sbomify.com/CVE-2025-10358/): Wavlink WL-WN578W2 wireless.cgi sub_404850 os command injection (medium 6.9)
- [CVE-2025-10359](https://insights.sbomify.com/CVE-2025-10359/): Wavlink WL-WN578W2 wireless.cgi sub_404DBC os command injection (medium 6.9)
- [CVE-2025-10321](https://insights.sbomify.com/CVE-2025-10321/): Wavlink WL-WN578W2 live_online.shtml information disclosure (medium 6.9)
- [CVE-2025-10323](https://insights.sbomify.com/CVE-2025-10323/): Wavlink WL-WN578W2 wizard_rep.shtml sub_409184 command injection (medium 6.9)
- [CVE-2025-10324](https://insights.sbomify.com/CVE-2025-10324/): Wavlink WL-WN578W2 firewall.cgi sub_401C5C command injection (medium 6.9)

## Fix prompt for AI coding agents

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

What it is: CVE-2025-10322 is a medium-severity vulnerability in Wavlink WL-WN578W2, published on 12 Sep 2025. 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-10322 exists.

Affected product: Wavlink WL-WN578W2. 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-10322/ (Markdown: https://insights.sbomify.com/CVE-2025-10322/index.md)
```

## Sources

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

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