Skip to main content

CVE-2025-6104: OS Command Injection in Wifi-soft UniBox Controller

High
VulnerabilityCVE-2025-6104cvecve-2025-6104
Published: Mon Jun 16 2025 (06/16/2025, 03:31:05 UTC)
Source: CVE Database V5
Vendor/Project: Wifi-soft
Product: UniBox Controller

Description

A vulnerability, which was classified as critical, was found in Wifi-soft UniBox Controller up to 20250506. This affects an unknown part of the file /billing/pms_check.php. The manipulation of the argument ipaddress leads to os command injection. It is possible to initiate 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.

AI-Powered Analysis

AILast updated: 06/16/2025, 04:04:31 UTC

Technical Analysis

CVE-2025-6104 is a critical security vulnerability identified in the Wifi-soft UniBox Controller, specifically affecting versions up to 20250506. The vulnerability resides in the /billing/pms_check.php file, where improper sanitization of the 'ipaddress' argument allows an attacker to perform OS command injection. This flaw enables remote attackers to execute arbitrary operating system commands on the affected device without requiring user interaction or prior authentication, significantly increasing the risk and ease of exploitation. The vulnerability was publicly disclosed on June 16, 2025, and although the vendor was notified early, no response or patch has been provided to date. The CVSS v4.0 score assigned is 8.7 (high severity), reflecting the vulnerability's network attack vector (AV:N), low attack complexity (AC:L), no privileges required (PR:L), no user interaction (UI:N), and high impact on confidentiality, integrity, and availability (VC:H/VI:H/VA:H). The exploitability is further emphasized by the fact that the vulnerability can be triggered remotely by manipulating the 'ipaddress' parameter, which is likely part of a web interface or API endpoint. The lack of vendor response and absence of patches increases the urgency for organizations to implement mitigations. Given the nature of the UniBox Controller as a network management or billing controller device, compromise could lead to unauthorized control over network infrastructure, data leakage, service disruption, or lateral movement within enterprise networks.

Potential Impact

For European organizations, the impact of CVE-2025-6104 could be severe, especially for those relying on Wifi-soft UniBox Controllers in their network infrastructure or billing systems. Successful exploitation could lead to full system compromise, allowing attackers to execute arbitrary commands, potentially leading to data breaches, manipulation of billing records, disruption of network services, or use of the compromised device as a pivot point for further attacks. This could affect telecommunications providers, ISPs, managed service providers, and enterprises with integrated network management solutions. The high integrity and availability impact could result in financial losses, reputational damage, regulatory penalties under GDPR if personal data is exposed, and operational downtime. The remote and unauthenticated nature of the exploit increases the risk of widespread attacks, especially in environments where these controllers are exposed to the internet or insufficiently segmented networks. Additionally, the absence of a vendor patch means organizations must rely on compensating controls, increasing operational complexity and risk.

Mitigation Recommendations

Given the lack of an official patch, European organizations should implement the following specific mitigations: 1) Immediately audit network architecture to identify all instances of Wifi-soft UniBox Controllers and assess their exposure, particularly to external networks. 2) Isolate affected devices behind strict firewall rules, limiting access to trusted management networks only, and block all unnecessary inbound traffic to the /billing/pms_check.php endpoint. 3) Employ Web Application Firewalls (WAFs) with custom rules to detect and block suspicious input patterns targeting the 'ipaddress' parameter, such as command injection payloads or shell metacharacters. 4) Monitor logs and network traffic for anomalous activity indicative of exploitation attempts, including unusual command execution or unexpected outbound connections from the controller. 5) If possible, disable or restrict the vulnerable functionality related to the 'ipaddress' parameter until a patch is available. 6) Engage with Wifi-soft or third-party security vendors for potential unofficial patches or mitigations. 7) Prepare incident response plans specifically addressing potential compromise of network controllers, including containment and recovery procedures. 8) Consider deploying network segmentation to limit lateral movement from compromised devices. These targeted actions go beyond generic advice by focusing on network exposure reduction, active detection, and containment strategies tailored to the specific vulnerability vector.

Need more detailed analysis?Get Pro

Technical Details

Data Version
5.1
Assigner Short Name
VulDB
Date Reserved
2025-06-15T09:41:05.453Z
Cvss Version
4.0
State
PUBLISHED

Threat ID: 684f9442a8c9212743838553

Added to database: 6/16/2025, 3:49:22 AM

Last enriched: 6/16/2025, 4:04:31 AM

Last updated: 8/19/2025, 7:37:57 AM

Views: 37

Actions

PRO

Updates to AI analysis are available only with a Pro account. Contact root@offseq.com for access.

Please log in to the Console to use AI analysis features.

Need enhanced features?

Contact root@offseq.com for Pro access with improved analysis and higher rate limits.

Latest Threats