CVE-2025-15067

Innorix · Innorix Innorix WP

A high-severity vulnerability has been identified in Innorix Innorix WP, which allows an unauthenticated attacker to upload malicious files, such as a web shell, to a vulnerable server.

Executive summary

A high-severity vulnerability has been identified in Innorix Innorix WP, which allows an unauthenticated attacker to upload malicious files, such as a web shell, to a vulnerable server. Successful exploitation could grant the attacker complete control over the affected web server, leading to potential data theft, service disruption, and further unauthorized access into the network.

Vulnerability

This vulnerability, classified as Unrestricted Upload of File with Dangerous Type (CWE-434), exists because the application fails to properly validate the type and content of files uploaded to the server. An attacker can exploit this by crafting a malicious file (e.g., a PHP, ASP, or JSP script disguised as a benign file type) and uploading it through the application's file upload functionality. Once the file is on the server, the attacker can navigate to it via a URL, causing the server to execute the code within the file and establishing a web shell for remote code execution.

Business impact

This vulnerability is rated as High severity with a CVSS score of 7.7. A successful exploit grants an attacker remote code execution capabilities on the web server, leading to significant business risks. These risks include the potential for a complete data breach, where an attacker can access, modify, and exfiltrate sensitive corporate or customer data. Additionally, the attacker could deface the website, disrupt critical services, or use the compromised server as a pivot point to launch further attacks against the internal network, causing severe reputational damage and financial loss.

Remediation

Immediate Action: The primary remediation is to apply the security updates provided by the vendor immediately across all affected systems. After patching, review web server access logs and file systems for any signs of compromise, such as suspicious uploaded files or unusual requests, that may have occurred prior to the patch deployment.

Proactive Monitoring: Implement enhanced monitoring to detect potential exploitation attempts. Review web server and application logs for POST requests to file upload endpoints containing suspicious file names or extensions (e.g., .php, .jsp, .aspx). Utilize File Integrity Monitoring (FIM) to alert on the creation of new executable files in web-accessible directories. Monitor network traffic for anomalous outbound connections from the web server, which could indicate a reverse shell or data exfiltration.

Compensating Controls: If immediate patching is not feasible, implement the following compensating controls to reduce risk:

  • Deploy a Web Application Firewall (WAF) with rules specifically configured to inspect and block the upload of files with dangerous or executable extensions.
  • If the file upload functionality is not critical, disable it entirely.
  • Configure the web server to prevent script execution within the designated upload directories.

Exploitation status

Public Exploit Available: false

Analyst recommendation

Given the high severity (CVSS 7.7) and the critical impact of remote code execution, this vulnerability poses a significant threat to the organization. We strongly recommend that organizations prioritize the immediate application of the vendor-supplied security patches. Although there is no evidence of active exploitation at this time, the ease with which this type of vulnerability can be exploited makes it a prime target for attackers. Proactive patching and monitoring are essential to prevent a potential compromise.