CVE-2023-51136
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 · uneditedTOTOLINK X2000R Gh v1.0.0-B20230221.0948.web was discovered to contain a stack overflow via the function formRebootSchedule.
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 · moderate confidenceA stack overflow vulnerability exists in the TOTOLINK X2000R Gh wireless router firmware (v1.0.0-B20230221.0948.web) within the formRebootSchedule web interface function. The stack overflow is exploitable remotely without authentication given the CVSS 9.8 score, and could potentially allow arbitrary code execution or device compromise.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data= 1.0.0-b20230221.0948.webCVSS 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
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
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 router firmware versionLog into the TOTOLINK X2000R web management interface and navigate to System Status or Firmware Upgrade page to view the current firmware version. Alternatively, check the firmware file name if you have direct access to the firmware image.Affected if The firmware version is exactly 1.0.0-B20230221.0948.web (only this specific version is listed as affected)
-
Confirm the specific router modelVerify that the device is specifically the TOTOLINK X2000R Gh model by checking the device label or the web interface status page.Affected if The device is a TOTOLINK X2000R Gh (the vulnerability is specific to this model)
-
Check web management interface accessibilityDetermine if the router web interface (typically on ports 80 or 443) is exposed to the network by checking your router network configuration settings under Administration, Access Control, or similar.Affected if The web management interface is accessible from untrusted network segments (the vulnerability is exploitable remotely without authentication)
-
Verify formRebootSchedule function existsAttempt to access the formRebootSchedule endpoint via HTTP POST request to the router (commonly at /cgi-bin/capi?formRebootSchedule or similar path under the router's web interface). The exact path can be discovered by analyzing the firmware or intercepting legitimate web requests.Affected if The formRebootSchedule function is present and responds to requests (this is the vulnerable component)
You are affected if you have a TOTOLINK X2000R Gh router running firmware version 1.0.0-B20230221.0948.web with the web interface accessible to the network and the formRebootSchedule function exposed.
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 dataApply vendor-supplied firmware updates when available; until then, restrict network access to the router's web management interface to trusted sources only.
- Consultation4.0 h
- Implementation2.0 h
- Testing4.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,392.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2023-51136 — 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-2023-51136 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