CVE-2026-7675
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 · uneditedA vulnerability has been found in Shenzhen Libituo Technology LBT-T300-HW1 up to 1.2.8. Impacted is the function start_lan of the file /apply.cgi. The manipulation of the argument Channel/ApCliSsid leads to buffer overflow. 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.
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 confidenceBuffer overflow vulnerability in Shenzhen Libituo LBT-T300-HW1 routers (firmware up to v1.2.8) in the /apply.cgi endpoint. The start_lan function fails to properly validate the Channel/ApCliSsid parameter, allowing remote attackers to overflow a buffer via crafted input. The exploit is publicly available and trivially exploitable over the network.
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
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:L/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 the device modelAccess the router admin interface or check the device label/sticker to confirm the model is Shenzhen Libituo LBT-T300-HW1Affected if Device is confirmed to be a Libituo LBT-T300-HW1 router
-
Check the firmware versionLog into the router admin panel and locate the firmware version information, typically found under Status, System Info, or Firmware Upgrade sectionsAffected if Firmware version is v1.2.8 or any version below 1.2.8
-
Verify network exposure of admin interfaceTest connectivity to the router's HTTP/HTTPS ports (typically 80/443) from untrusted networks. Use an external port scanner or attempt to access /apply.cgi from outside your trusted networkAffected if The /apply.cgi endpoint is reachable from untrusted/networked interfaces without firewall restriction
-
Check for indicators of compromiseReview router logs for unusual POST requests to /apply.cgi, especially those with abnormally long strings in the Channel or ApCliSsid parameters. Monitor for unexpected configuration changes or new admin accountsAffected if Log entries show suspicious long parameter values in /apply.cgi requests or unexpected configuration modifications
You are affected if the device is a Libituo LBT-T300-HW1 router running firmware v1.2.8 or lower AND the /apply.cgi administrative endpoint is exposed to untrusted networks.
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 dataSince the vendor is unresponsive, immediately restrict administrative interface exposure to trusted networks only using firewall rules or VLAN segmentation. Monitor for signs of exploitation and consider device replacement if no firmware update becomes available.
- Consultation4.0 h
- Implementation2.0 h
- Testing6.0 h
- Review / QA3.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,160.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-7675 — 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-2026-7675 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