CVE-2026-31067
Remote Command Execution in UTT Aggressive 520W /goform/formReleaseConnect
Publication date: 2026-04-06
Last updated on: 2026-04-07
Assigner: MITRE
Description
Description
CVSS Scores
EPSS Scores
| Probability: | |
| Percentile: |
Meta Information
Affected Vendors & Products
| Vendor | Product | Version / Range |
|---|---|---|
| utt | 520w_firmware | 1.7.7-180627 |
Helpful Resources
Exploitability
| CWE ID | Description |
|---|---|
| CWE-78 | The product constructs all or part of an OS command using externally-influenced input from an upstream component, but it does not neutralize or incorrectly neutralizes special elements that could modify the intended OS command when it is sent to a downstream component. |
Attack-Flow Graph
AI Powered Q&A
Can you explain this vulnerability to me?
CVE-2026-31067 is a critical remote command execution vulnerability in the UTT Aggressive 520W router firmware versions up to v3v1.7.7-180627. It occurs in the /goform/formReleaseConnect component, where the "Isp_Name" parameter from an HTTP POST request is improperly handled.
When the "Isp_Name" parameter is not empty, its value is directly passed into a system command executed by the router, allowing an attacker to inject arbitrary shell commands.
An attacker can send a crafted POST request with malicious commands embedded in the "Isp_Name" parameter, which the router executes with system-level privileges, potentially compromising the entire device.
How can this vulnerability impact me? :
This vulnerability allows remote attackers who have access to the routerβs web interface to execute arbitrary system commands with the privileges of the routerβs system process.
As a result, an attacker could fully compromise the device, potentially gaining control over network traffic, modifying router settings, or using the device as a foothold to attack other devices on the network.
How can this vulnerability be detected on my network or system? Can you suggest some commands?
This vulnerability can be detected by sending a crafted HTTP POST request to the vulnerable router's endpoint `/goform/formReleaseConnect` with the "Isp_Name" parameter containing shell commands. The request requires Digest authentication with valid credentials.
A proof of concept involves sending a POST request with the "Isp_Name" parameter set to a command injection payload, such as `;ls / > /etc_ro/web/1.txt;`, which executes the `ls /` command and writes the output to a file on the routerβs filesystem.
- Use a tool like curl to send the POST request with Digest authentication and the crafted payload.
- Example command (replace USER, PASS, ROUTER_IP accordingly):
- curl -X POST -u USER:PASS --digest -d "Isp_Name=;ls / > /etc_ro/web/1.txt;" http://ROUTER_IP/goform/formReleaseConnect
After sending the request, check the routerβs filesystem or web-accessible directories for the output file (e.g., `/etc_ro/web/1.txt`) to confirm command execution.
How does this vulnerability affect compliance with common standards and regulations (like GDPR, HIPAA)?:
The CVE-2026-31067 vulnerability allows remote attackers to execute arbitrary commands on the UTT Aggressive 520W router, potentially leading to full device compromise.
Such a compromise could result in unauthorized access to sensitive data or disruption of network services, which may violate requirements for data protection and security under common standards and regulations like GDPR and HIPAA.
However, the provided information does not explicitly detail the impact on compliance with these standards.
What immediate steps should I take to mitigate this vulnerability?
To mitigate the CVE-2026-31067 vulnerability, immediately restrict access to the router's web interface to trusted users only, as exploitation requires valid Digest authentication credentials.
Avoid using firmware versions up to v3v1.7.7-180627 that are vulnerable; check for and apply any available firmware updates or patches from the vendor.
Monitor and audit router logs for any suspicious POST requests to the /goform/formReleaseConnect endpoint, especially those containing unusual or crafted 'Isp_Name' parameter values.
If possible, disable or restrict the /goform/formReleaseConnect functionality or the affected parameter until a patch is applied.