dbcve.org
Memory Buffer Bounds ErrorWeakness · CWE-119

CVE-2026-6563

HIGH · 8.8 CVSS v3.1 Published 2026-04-19
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
94/100
Remediation priority · Urgent
Remotely reachable Zero-click

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 · unedited
A vulnerability has been found in H3C Magic B1 up to 100R004. The affected element is the function SetAPWifiorLedInfoById of the file /goform/aspForm. The manipulation of the argument param leads to buffer overflow. It is possible to initiate the attack 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 confidence

Buffer overflow vulnerability in H3C Magic B1 router's web interface function SetAPWifiorLedInfoById in /goform/aspForm. The param argument is not properly bounds-checked, allowing remote attackers to overflow a buffer via crafted HTTP requests to this form handler.

MitigationSince the vendor did not respond, apply network-level controls: disable remote web management exposure to the internet, place device behind a firewall, or restrict management access to trusted IPs only. Consider replacing the device if no firmware update becomes 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 checks

Work through these to decide whether this CVE applies to you.

  1. Confirm device model is H3C Magic B1
    Access the router web interface and check the device information page, or inspect the device label. You can also query the device via HTTP headers or management interface to identify the model.
    Affected if The device model is not H3C Magic B1, the vulnerability does not apply.
  2. Check if web management interface is enabled and accessible
    Attempt to access the router login page at the default gateway IP (commonly 192.168.1.1) via HTTP/HTTPS. Verify the web service responds.
    Affected if The web interface is not running or not accessible, exploitation is not possible via this vector.
  3. Determine if remote web management is exposed
    Check router settings for 'remote management' or 'WAN access' options. Test by accessing the public IP of the router on ports 80/443 from an external network, or review firewall rules.
    Affected if Remote management is enabled and the web interface is exposed to untrusted networks, the device is vulnerable to remote attack.
  4. Identify firmware version
    Login to the router web interface and navigate to System Settings, Status, or About page to find the firmware version. Alternatively, check the vendor support site for H3C Magic B1 firmware releases.
    Affected if Firmware version matches known affected versions (compare your installed version to the affected ranges provided by H3C).
  5. Verify the aspForm endpoint exists
    Send a crafted HTTP request to /goform/aspForm on the router's IP address. Use browser developer tools or curl to inspect if the endpoint responds.
    Affected if The /goform/aspForm endpoint is present and accepts the SetAPWifiorLedInfoById function parameter, the buffer overflow vulnerability is present.

You are affected if you own an H3C Magic B1 router with its web interface accessible (especially remotely) and running a firmware version within the affected range that contains the vulnerable SetAPWifiorLedInfoById function in /goform/aspForm.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Since the vendor did not respond, apply network-level controls: disable remote web management exposure to the internet, place device behind a firewall, or restrict management access to trusted IPs only. Consider replacing the device if no firmware update becomes available.

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA2.0 h
11.0 hours of engineering $1,930
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,088.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-6563 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-6563 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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