CVE-2025-56311
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedIn 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.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · high confidenceThe FD602GW-DX-R410 router firmware v2.2.14 lacks CSRF protection on the /boaform/admin/formReboot endpoint. An authenticated administrator visiting a malicious webpage can unknowingly trigger a device reboot, causing denial of service.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- Low
- Integrity
- Low
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:N
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Identify device model and firmware versionAccess the router web interface admin panel and navigate to the System or Status page to view the device model (FD602GW-DX-R410) and firmware version. Alternatively, check the footer or login page for version information.Affected if The device is FD602GW-DX-R410 and the firmware version is v2.2.14 or lower.
-
Locate the formReboot endpointAccess the router web interface and identify if a reboot function exists. The vulnerable endpoint is /boaform/admin/formReboot - try navigating to or inspecting forms that trigger a device reboot.Affected if The /boaform/admin/formReboot endpoint exists and is accessible via the web interface.
-
Check for CSRF token presence in reboot formView the HTML source of the reboot form or any page containing the formReboot submission mechanism. Look for hidden input fields containing anti-CSRF tokens, or check if the form submission includes token parameters.Affected if No anti-CSRF token (synchronizer token) is present in the form or request parameters when submitting to formReboot.
-
Verify SameSite cookie attributeUse browser developer tools to inspect cookies set by the router web application. Check if the session cookie has the SameSite attribute set to Strict or Lax, or if it is missing the attribute entirely.Affected if The session cookie lacks SameSite=Strict or SameSite=Lax attributes, or no CSRF protection mechanism is detected.
The device is affected if it is an FD602GW-DX-R410 router running firmware v2.2.14 or lower, the /boaform/admin/formReboot endpoint exists, and no anti-CSRF tokens or SameSite cookie protections are present on that endpoint.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
From vendor dataImplement anti-CSRF tokens or validation (e.g., synchronizer token pattern, SameSite cookies, or Referer/Origin header checks) on the formReboot endpoint to verify request authenticity.
- Consultation2.0 h
- Implementation4.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,560.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-56311 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2025-56311 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data