CVE-2026-7218
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 was detected in Totolink N300RT 3.4.0-B20250430. The impacted element is the function is_cmd_string_valid of the file /boafrm/formWsc of the component libapmib.so. Performing a manipulation of the argument localPin results in buffer overflow. The attack is possible to be carried out remotely. The exploit is now public and may be used.
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 in the is_cmd_string_valid function within libapmib.so (/boafrm/formWsc) of Totolink N300RT firmware 3.4.0-B20250430 allows remote attackers to overflow the localPin parameter, potentially leading to code execution. The vulnerability affects the WSC (Wi-Fi Simple Config) web interface component.
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
- High
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:H/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's web administrative interface or check the device label/metadata to confirm the model is Totolink N300RTAffected if The device is not a Totolink N300RT router - this vulnerability only affects this specific model
-
Check the firmware versionLog into the router web interface and navigate to System Status or Firmware Upgrade page to view the current firmware version, or use the router's admin CLI if availableAffected if The firmware version matches v3.4.0-B20250430 exactly, or falls within the range containing this version (v3.4.0-B20250430 and related builds)
-
Verify the vulnerable web component existsCheck if the file /boafrm/formWsc is accessible on the router's web server by attempting to access http://<router-ip>/boafrm/formWsc or by examining the firmware image for the presence of this CGI handlerAffected if The /boafrm/formWsc endpoint is present and responds to requests
-
Confirm WPS/WSC functionality is enabledLog into the router admin panel and check Wireless Settings > WPS (Wi-Fi Protected Setup) or WSC (Wi-Fi Simple Config) settings to see if this feature is enabledAffected if WPS/WSC functionality is enabled on the device - the buffer overflow occurs through the localPin parameter to this feature
-
Check for the vulnerable libraryIf firmware extraction is possible, locate libapmib.so within the firmware filesystem and verify the is_cmd_string_valid function exists within itAffected if The libapmib.so library contains the is_cmd_string_valid function and it performs insufficient bounds checking on the localPin parameter
The device is affected if it is a Totolink N300RT running firmware v3.4.0-B20250430 or a related version, with the /boafrm/formWsc endpoint present and WPS/WSC functionality enabled.
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 firmware update when available; if no update exists, restrict access to the router's web management interface to trusted networks only to reduce remote attack surface.
- Consultation2.0 h
- Implementation4.0 h
- Testing3.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,800.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-7218 — 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-7218 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