CVE-2026-9393
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 found in H3C Magic B0 up to 100R002. This affects the function Edit_BasicSSID_5G of the file /goform/aspForm. Performing a manipulation of the argument param results in buffer overflow. The attack may be initiated remotely. The exploit has been made public and could 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 confidenceA buffer overflow vulnerability exists in H3C Magic B0 routers (up to version 100R002) in the Edit_BasicSSID_5G function within /goform/aspForm. The vulnerability is exploitable remotely by manipulating the param argument, allowing potential arbitrary code execution or denial of service. A public exploit is available.
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's web admin interface or check the device label. Look for 'H3C Magic B0' or 'Magic B0' in the product name/model information.Affected if The device is an H3C Magic B0 router.
-
Check the firmware versionLog into the router admin panel and navigate to System Status or Firmware Upgrade page. Note the firmware version number displayed (e.g., 100R002).Affected if The firmware version is 100R002 or any version lower than it.
-
Verify web management interface accessibilityAttempt to access the router's login page from an external network (outside the local LAN). Check if port 80 or 443 is reachable from the WAN interface.Affected if The router's web interface is accessible from the WAN/internet.
-
Confirm the aspForm endpoint existsSend an HTTP GET request to http://<router-ip>/goform/aspForm and check for a valid response (authentication prompt or error).Affected if The /goform/aspForm endpoint responds to requests.
-
Check if remote management is enabledIn the router admin panel, look under Advanced Settings, Administration, or Security settings for 'Remote Management' or 'Remote Access' configuration. Verify if it is set to allow access from WAN.Affected if Remote management/WAN access to the web interface is enabled.
If the device is an H3C Magic B0 router running firmware version 100R002 or below AND its web management interface (specifically the /goform/aspForm endpoint) is accessible from the network where an attacker could reach it, the environment is affected by this vulnerability.
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 no vendor patch is available, restrict network access to the device's management interface, implement network segmentation, and consider replacing the device with a supported model. If the device must remain in service, monitor for exploitation attempts.
- Consultation6.0 h
- Implementation24.0 h
- Testing12.0 h
- Review / QA6.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $13,440.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-9393 — 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-9393 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