CVE-2026-7420
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 security flaw has been discovered in UTT HiPER 1250GW up to 3.2.7-210907-180535. Impacted is the function strcpy of the file route/goform/ConfigAdvideo. The manipulation of the argument Profile results in buffer overflow. The attack can be executed remotely. The exploit has been released to the public and may be used for attacks.
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 UTT HiPER 1250GW router firmware (up to version 3.2.7-210907-180535) in the ConfigAdvideo web form handler. The unsafe strcpy function copies the Profile parameter without bounds checking, allowing remote attackers to overflow a buffer via crafted HTTP requests.
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 model is UTT HiPER 1250GWAccess the router web interface and navigate to the status or system information page to verify the exact model number, or physically inspect the device label.Affected if Device model is UTT HiPER 1250GW and firmware version is 3.2.7-210907-180535 or earlier
-
Check installed firmware versionLog into the router admin panel, typically at 192.168.1.1 or 192.168.0.1, and locate the firmware version under System > Firmware Upgrade, Status, or About sections.Affected if Firmware version is 3.2.7-210907-180535 or any version prior to it (the vulnerability affects up to this version)
-
Verify ConfigAdvideo web form handler existsAttempt to access the ConfigAdvideo form via HTTP request to common paths such as /ConfigAdvideo.asp, /cgi-bin/ConfigAdvideo, or /goform/ConfigAdvideo, or locate it in the router web interface menus.Affected if The ConfigAdvideo form handler is present and accessible on the device
-
Determine if web management interface is remotely accessibleCheck the router admin panel under System > Remote Management, Administration > Remote Access, or similar settings to see if WAN/remote access to the web interface is enabled.Affected if Remote administration is enabled, allowing the vulnerable form to be reached from outside the local network
The device is affected if it is a UTT HiPER 1250GW running firmware version 3.2.7-210907-180535 or earlier, and the ConfigAdvideo form handler is accessible either locally or remotely.
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 router's web management interface to trusted networks or disable remote administration to reduce attack surface.
- Consultation4.0 h
- Implementation2.0 h
- Testing3.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,152.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-7420 — 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-7420 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