CVE-2026-10293
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 flaw has been found in UTT HiPER 1200GW up to 2.5.3-170306. This impacts the function strcpy of the file /goform/formFireWall. This manipulation of the argument Profile causes stack-based buffer overflow. Remote exploitation of the attack is possible. The exploit has been published 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 vulnerability in the UTT HiPER 1200GW router's web interface (file /goform/formFireWall) where the unsafe strcpy function copies user-supplied input from the Profile parameter without bounds checking, allowing remote attackers to overflow a stack buffer.
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 interface or check the device label/marketing to confirm it is a UTT HiPER 1200GW routerAffected if The device is not a UTT HiPER 1200GW, then it is not affected by this specific vulnerability
-
Check the firmware versionLog into the router web interface and look for a firmware version display (typically under Status, System, or About pages), or use the command 'cat /proc/version' or 'cat /etc/version' if you have shell accessAffected if The installed firmware version is 2.5.3-170306 or any earlier version (versions higher than 2.5.3-170306 are not affected)
-
Verify the web management interface is accessibleAttempt to access the router's web interface over HTTP or HTTPS on the LAN or WAN IP address, specifically navigate to the /goform/formFireWall endpointAffected if The router's web interface with the formFireWall endpoint is accessible (this is the attack surface for the vulnerability)
-
Confirm the Profile parameter exists in formFireWallSubmit a GET or POST request to /goform/formFireWall and inspect whether a 'Profile' parameter is accepted by the form (this is the vulnerable parameter)Affected if The formFireWall interface accepts a 'Profile' parameter without proper input validation, the device is vulnerable to the strcpy overflow
If the device is a UTT HiPER 1200GW router running firmware version 2.5.3-170306 or earlier AND the web interface with formFireWall and Profile parameter is accessible, then the environment is affected by CVE-2026-10293.
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 available vendor firmware update; until patched, restrict remote access to the device's web management interface via firewall rules or disable WAN-facing administration.
- 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-10293 — 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-10293 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