CVE-2026-10292
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 UTT HiPER 1200GW up to 2.5.3-170306. This affects the function strcpy of the file /goform/formTaskEdit. The manipulation results in stack-based buffer overflow. The attack may be launched 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 · high confidenceStack-based buffer overflow in the UTT HiPER 1200GW router web interface (/goform/formTaskEdit) via the unsafe strcpy function. The vulnerability allows remote attackers to overflow a stack-allocated buffer, potentially enabling arbitrary code execution. The exploit is publicly available, increasing risk.
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 web interface or check the device label/marketing materials for the exact model number. Confirm it is a UTT HiPER 1200GW router.Affected if The device is a UTT HiPER 1200GW router.
-
Locate the web interfaceAttempt to access the router web interface by entering the router IP address in a web browser. Look for a login page, typically on port 80 or 443.Affected if The router web interface is accessible on the network.
-
Identify the firmware versionLog into the router web interface and navigate to the System Status, Firmware Version, or About page to find the installed firmware version.Affected if The installed firmware version is unpatched (no official patch available for this CVE).
-
Check for the vulnerable endpointAttempt to access the URI /goform/formTaskEdit directly via a web request (e.g., GET or POST). A response (even an error) indicates the endpoint exists.Affected if The /goform/formTaskEdit endpoint is present and responds to requests.
-
Determine if remote management is enabledIn the router web interface, look for settings named Remote Management, Remote Access, Web Access from WAN, or Administration Access. Check if HTTP/HTTPS access from WAN/internet is permitted.Affected if Remote management or web access from WAN is enabled, allowing unauthenticated or authenticated attackers to reach the vulnerable endpoint from the internet.
A user is affected if they own a UTT HiPER 1200GW router with an unpatched firmware version and the router web interface (specifically the /goform/formTaskEdit endpoint) is accessible, especially from 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 dataApply vendor firmware patch when available; until then, restrict network access to the router's web management interface to trusted IPs only, or disable remote web management if not required.
- Consultation2.0 h
- Implementation1.0 h
- Testing2.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 $1,696.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-10292 — 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-10292 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