CVE-2026-4487
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 determined in UTT HiPER 1200GW up to 2.5.3-170306. This impacts the function strcpy of the file /goform/websHostFilter. This manipulation causes buffer overflow. It is possible to initiate the attack remotely. The exploit has been publicly disclosed and may be utilized.
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 confidenceBuffer overflow vulnerability in the strcpy function within /goform/websHostFilter of UTT HiPER 1200GW router firmware up to version 2.5.3-170306. The unsafe strcpy call does not perform bounds checking when processing web form input, allowing an attacker to overflow the destination buffer and potentially execute arbitrary code remotely.
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.
-
Confirm device modelAccess the router web management interface or check device labeling to verify the model is UTT HiPER 1200GWAffected if Device is not an UTT HiPER 1200GW router
-
Check firmware versionLog into the router web interface and navigate to Status or System Information page to view the firmware version. Alternatively, check via CLI if available.Affected if Firmware version is 2.5.3-170306 or any version prior to it
-
Verify websHostFilter endpoint existsSend an HTTP GET or POST request to http://<device_ip>/goform/websHostFilter and observe the response. A valid endpoint will return a response rather than a 404 error.Affected if The /goform/websHostFilter endpoint is accessible and responds to requests
-
Check web management interface exposureDetermine if the router web interface is accessible from WAN/internet ports (remote administration). Check router settings for 'Remote Management' or 'Web Access from WAN' options.Affected if Remote administration is enabled and the web interface is reachable from untrusted networks
-
Inspect Host Filter configurationAccess the web management interface and navigate to the Host Filter or Access Control settings page where /goform/websHostFilter is used.Affected if The Host Filter feature is configured and enabled on the device
The device is affected if it is a UTT HiPER 1200GW running firmware version 2.5.3-170306 or earlier, the /goform/websHostFilter endpoint is accessible, and the Host Filter feature is in use.
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 update if available; otherwise restrict access to the device's web management interface to trusted networks or disable remote administration.
- Consultation4.0 h
- Implementation8.0 h
- Testing6.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $6,176.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-4487 — 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-4487 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