Memory Buffer Bounds ErrorWeakness · CWE-119

CVE-2026-14721

HIGH · 8.8 CVSS v3.1 Published 2026-07-05
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 7 weeks old

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 UTT HiPER 1250GW up to 3.2.7-210907-180535. This affects an unknown function of the file /goform/ConfigWirelessBase_5g of the component Web Endpoint. The manipulation of the argument ssid leads to stack-based buffer overflow. The attack is possible to be carried out remotely. The exploit has been disclosed to the 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 confidence

Stack-based buffer overflow in UTT HiPER 1250GW router firmware's web endpoint /goform/ConfigWirelessBase_5g. The ssid parameter is not properly bounds-checked before being copied to a fixed-size stack buffer, allowing remote attackers to overwrite return addresses and potentially execute arbitrary code.

MitigationApply vendor firmware update when available. Until then, restrict access to the router's web management interface to trusted networks only, disable remote administration, and consider network segmentation.

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. Identify the device model
    Access the router's web interface or check the device label/marketing, or query the web interface for the model information (often visible in the login page or status page)
    Affected if The device is not a UTT HiPER 1250GW router, as this vulnerability only affects that specific model
  2. Confirm firmware version
    Log into the router's web management interface and navigate to the status or system information page to view the installed firmware version
    Affected if The firmware version has not been patched by the vendor; since no patched version is specified, compare your version against any release notes from UTT or assume all current versions may be affected
  3. Verify web management interface accessibility
    Attempt to access the router's web interface from an external network (WAN side) by navigating to the router's public IP address on HTTP/HTTPS ports
    Affected if The web management interface is reachable from the WAN (internet), as remote attackers exploit this vulnerability over the network without authentication
  4. Check if ConfigWirelessBase_5g endpoint is reachable
    Send an HTTP GET or POST request to http://<router-ip>/goform/ConfigWirelessBase_5g using a tool like curl or a browser
    Affected if The endpoint responds (indicating the wireless configuration interface is active and accessible), which is required for the overflow to be triggered
  5. Determine if 5GHz wireless is enabled
    Log into the router and check the wireless settings to see if the 5GHz band is configured and enabled
    Affected if 5GHz wireless is enabled on the device, as the vulnerable parameter is part of the /goform/ConfigWirelessBase_5g endpoint processing

A user is affected if they own a UTT HiPER 1250GW router with an unpatched firmware version and the router's web management interface (especially the wireless configuration endpoint) is accessible to untrusted networks.

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

Apply vendor firmware update when available. Until then, restrict access to the router's web management interface to trusted networks only, disable remote administration, and consider network segmentation.

Have this fixed Scoped from the published advisory
  • Consultation6.0 h
  • Implementation16.0 h
  • Testing8.0 h
  • Review / QA4.0 h
34.0 hours of engineering $6,000
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-14721 — 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 sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-14721 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