dbcve.org
512w FirmwareOperating system · Utt

CVE-2025-14191

CRITICAL · 9.8 CVSS v3.1 Published 2025-12-07
Fix available
A fix is available. Upgrade to after 1.7.7-171114 or later.
See remediation →
100/100
Remediation priority · Urgent
Public exploit Remotely reachable No privileges Zero-click

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 进取 512W up to 1.7.7-171114. Affected by this issue is the function strcpy of the file /goform/formP2PLimitConfig. Such manipulation of the argument except leads to buffer overflow. It is possible to launch the attack remotely. The exploit has been disclosed to the public and may be used. The vendor was contacted early about this disclosure but did not respond in any way.

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 confidence

Buffer overflow vulnerability in UTT 进取 512W router firmware (versions up to 1.7.7-171114) in the /goform/formP2PLimitConfig function where unsafe strcpy copies user-controlled input without bounds checking, allowing remote attackers to potentially execute arbitrary code.

MitigationSince the vendor did not respond and no patch is available, immediately restrict network access to the router's management interface via firewall rules or network segmentation; replace the device if no firmware update becomes available.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
512w FirmwareOperating system
Affected:<= 1.7.7-171114

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
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/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. Confirm device model is the affected UTT 512W router
    Access the router's web management interface or check the device label/documentation to verify the exact model is 'UTT 进取 512W' or 'Utt 512w'. Other UTT models are not affected by this specific CVE.
    Affected if The device is not the UTT 进取 512W model, then this specific CVE does not apply.
  2. Identify the installed firmware version
    Log into the router's web administration panel and navigate to the status or system information page to view the firmware version. Alternatively, check for a firmware version display in the device GUI or through the command line if SSH/Telnet access is available.
    Affected if The firmware version is 1.7.7-171114 or any version lower than this (for example, 1.7.6-XXXXXX), meaning the version is at or below the affected range.
  3. Verify the web management interface is accessible
    Attempt to access the router's web interface by entering the router's IP address in a web browser. The vulnerable function is at /goform/formP2PLimitConfig, which is a web form endpoint.
    Affected if The web management interface is exposed and reachable on the network. If the interface is not accessible at all, the vulnerable code path cannot be triggered.
  4. Confirm the vulnerable formP2PLimitConfig endpoint exists
    Send an HTTP request to http://[router-ip]/goform/formP2PLimitConfig or access this path through the browser. A valid response (even an error page) indicates the endpoint is present in the firmware.
    Affected if The /goform/formP2PLimitConfig endpoint responds, indicating the vulnerable function is included in the deployed firmware version.

A user is affected if they have a UTT 进取 512W router running firmware version 1.7.7-171114 or lower, with the router's web management interface accessible on the network.

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
Upgrade available Upgrade to a release after 1.7.7-171114
Interim mitigation

Since the vendor did not respond and no patch is available, immediately restrict network access to the router's management interface via firewall rules or network segmentation; replace the device if no firmware update becomes available.

Fix this in 512w Firmware Scoped from the published advisory
  • Consultation8.0 h
  • Implementation4.0 h
  • Testing12.0 h
  • Review / QA6.0 h
30.0 hours of engineering $5,200
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-14191 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

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-2025-14191 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