Description

A vulnerability has been identified in Siveillance Control Pro V3.0 (All versions < V3.0.12.2173), Siveillance Control Pro V4.0 (All versions < V4.0.9.2178), Siveillance Control V3.0 (All versions < V3.0.22.2177), Siveillance Control V4.0 (All versions < V4.0.11.2177). A vulnerability in the OIS web module allows an attacker to upload arbitrary files to the server. Successful exploitation of this vulnerability could allow an attacker to gain root access on the host system, potentially leading to a full compromise of the affected OIS environment.

Executive Summary

Technical Details

Mitigations

References

Additional Metadata

{
  "score": "9.0",
  "pubDate": "2026-09-08T09:18:10.733Z",
  "pubdate": "2026-09-08T09:18:10.733Z",
  "executiveSummary": "A critical arbitrary file upload vulnerability exists within the OIS web module of Siveillance Control Pro and Siveillance Control platforms.\nThe vulnerability stems from improper validation of file uploads, enabling an unauthenticated or authenticated attacker to upload arbitrary files to the server.\nSuccessful exploitation permits remote code execution, granting the attacker the ability to execute commands with root-level privileges on the host operating system.\nThe affected product versions include Siveillance Control Pro V3.0 (all versions < V3.0.12.2173), Siveillance Control Pro V4.0 (all versions < V4.0.9.2178), Siveillance Control V3.0 (all versions < V3.0.22.2177), and Siveillance Control V4.0 (all versions < V4.0.11.2177).\nThe risk is categorized as critical, as it facilitates complete system compromise, potential lateral movement within the network, and total loss of confidentiality, integrity, and availability of the affected OIS environment.",
  "technicalDetails": "The vulnerability resides within the OIS (Open Integration Services) web module, which acts as an interface for data exchange and system management.\nThe root cause of this vulnerability is the lack of strict server-side input validation and sanitization on the file upload mechanisms provided by the web interface. The application fails to verify the file extension, MIME type, or content of uploaded files before storing them in a web-accessible directory.\nExploitation involves an attacker crafting a malicious payload, typically a web shell (e.g., a PHP, ASPX, or JSP script depending on the underlying server architecture), and submitting it via the vulnerable upload endpoint. Because the server does not enforce restrictions on file types, the malicious script is successfully written to the server's filesystem.\nThe attack flow proceeds as follows: First, the attacker identifies the web module endpoint that handles file uploads. Second, the attacker sends an HTTP POST request containing the malicious file. Third, upon successful upload, the attacker accesses the file via a direct URL request to the web server. Finally, the server processes the file, executing the embedded code within the security context of the web server service.\nGiven that the OIS web module often runs with elevated system permissions, the successful execution of an uploaded script results in the attacker inheriting these permissions. This allows for root or SYSTEM level access, effectively providing full control over the host OS.\nPost-exploitation impact is severe, including the ability to install persistent backdoors, dump sensitive credentials from system memory, exfiltrate proprietary data from the Siveillance environment, and deploy additional malicious payloads to facilitate lateral movement throughout the corporate or operational technology (OT) network.\nThis vulnerability is particularly dangerous as it provides a remote path to system-wide compromise without requiring existing credentials, assuming the OIS web module is exposed to the network. The ability to overwrite or create files in critical directories enables the attacker to manipulate system configuration files or replace legitimate application binaries to maintain long-term persistence even after a reboot."
}