# CVE-2025-56311: Cross-site request forgery in n/a

> An attacker can force a router reboot via CSRF, causing denial of service, affecting C-Data FD602GW-DX-R410 administrators.

- **Severity:** Medium 6.5 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 23 Sep 2025
- **Updated:** 28 Oct 2025
- **Also known as:** GHSA-2746-jhfw-vv95

## What is CVE-2025-56311?

CVE-2025-56311 is a medium-severity vulnerability in n/a, published on 23 Sep 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

In Shenzhen C-Data Technology Co. FD602GW-DX-R410 (firmware v2.2.14), the web management interface contains an authenticated CSRF vulnerability on the reboot endpoint (/boaform/admin/formReboot). An attacker can craft a malicious webpage that, when visited by an authenticated administrator, causes the router to reboot without explicit user consent. This lack of CSRF protection on a sensitive administrative function can lead to denial of service by disrupting network availability.

Weakness: CWE-352 (Cross-Site Request Forgery)

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


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

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

## Is CVE-2025-56311 being exploited?

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

Public exploit code:

- CSRF vulnerability in FD602GW-DX-R410 router allows remote attackers to reboot the device via a crafted POST request to /boaform/admin/formReboot when an admin is authenticated. (github_poc): https://github.com/wrathfulDiety/CVE-2025-56311

## Fix prompt for AI coding agents

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

What it is: CVE-2025-56311 is a medium-severity vulnerability in n/a, published on 23 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-56311 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-56311/ (Markdown: https://insights.sbomify.com/CVE-2025-56311/index.md)
```

## Sources

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

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