Overview
In this blog post, we delve into the details of a critical vulnerability found in Wifi-soft UniBox Controller. This vulnerability, identified as CVE-2025-6104, affects all versions up to 20250506. It has been classified as critical due to its potential to compromise systems and lead to data leakage. The exploitation of this vulnerability could have significant implications for organizations using the affected product, as it can be exploited remotely, leading to unauthorized access and control of systems.
Vulnerability Summary
CVE ID: CVE-2025-6104
Severity: Critical (8.8 CVSS Score)
Attack Vector: Network
Privileges Required: None
User Interaction: None
Impact: Potential system compromise and data leakage
Affected Products
Escape the Surveillance Era
Most apps won’t tell you the truth.
They’re part of the problem.
Phone numbers. Emails. Profiles. Logs.
It’s all fuel for surveillance.
Ameeba Chat gives you a way out.
- • No phone number
- • No email
- • No personal info
- • Anonymous aliases
- • End-to-end encrypted
Chat without a trace.
Product | Affected Versions
Wifi-soft UniBox Controller | up to 20250506
How the Exploit Works
The vulnerability lies in the /billing/pms_check.php file of the Wifi-soft UniBox Controller. It is triggered when an attacker manipulates the ‘ipaddress’ argument to inject malicious OS commands. The software does not properly sanitize the ‘ipaddress’ input, which allows an attacker to execute arbitrary OS commands. The nature of the vulnerability suggests that it can be exploited remotely over a network without requiring any user interaction.
Conceptual Example Code
Below is a conceptual example of how an HTTP request might be manipulated to exploit this vulnerability:
POST /billing/pms_check.php HTTP/1.1
Host: target.example.com
Content-Type: application/x-www-form-urlencoded
ipaddress=127.0.0.1; cat /etc/passwdIn this example, the attacker injects the OS command ‘cat /etc/passwd’ after the ‘ipaddress’ parameter. If successful, this would allow the attacker to view the system’s password file.
Recommended Mitigation
As of now, the vendor has not responded to this vulnerability disclosure. Therefore, we recommend adopting the following mitigation strategies:
* Apply a vendor patch as soon as it becomes available
* Implement a Web Application Firewall (WAF) or Intrusion Detection System (IDS) as a temporary mitigation measure
* Regularly update and patch your systems to protect against known vulnerabilities
Remember, staying informed and proactive in addressing vulnerabilities is a critical part of any cybersecurity strategy.