CVE-2025-54948
Trend · Trend Micro Apex One (on-premise)
A critical vulnerability has been identified in the Trend Micro Apex One management console, which could allow a remote attacker to gain complete control of the system without needing any credentials.
Executive summary
A critical vulnerability has been identified in the Trend Micro Apex One management console, which could allow a remote attacker to gain complete control of the system without needing any credentials. Successful exploitation could lead to the compromise of the entire endpoint security infrastructure, enabling an attacker to disable security protections, deploy malware such as ransomware, or steal sensitive data from the network. Due to the high severity and ease of exploitation, immediate patching is strongly recommended.
Vulnerability
This is a pre-authentication remote code execution (RCE) vulnerability within the Trend Micro Apex One management console. An unauthenticated attacker, with network access to the console, can exploit this flaw by uploading a specially crafted malicious file. Once uploaded, the attacker can execute arbitrary commands on the underlying server with the privileges of the Apex One application, leading to a full system compromise.
Business impact
This vulnerability is rated as critical severity with a CVSS score of 9.4. A successful attack would result in the complete compromise of the Trend Micro Apex One server, which is a central component of an organization's endpoint security strategy. An attacker could leverage this access to disable security policies, un-install security agents from endpoints, deploy ransomware across the network, exfiltrate sensitive corporate data, or use the compromised server as a pivot point to launch further attacks within the internal network. The pre-authentication nature of this vulnerability significantly increases the risk, as it lowers the barrier for potential attackers.
Remediation
Immediate Action: Immediately apply the security patches released by Trend Micro to update Apex One to the latest, non-vulnerable version. After patching, it is crucial to review historical web and application logs for any indicators of compromise that may have occurred prior to the patch being applied.
Proactive Monitoring: Monitor for signs of exploitation by looking for unusual file uploads to the Apex One web directories, especially files with extensions like .jsp, .aspx, or .php. Scrutinize server logs for unexpected child processes being spawned by the Apex One services (e.g., cmd.exe, powershell.exe). Network monitoring should be configured to detect and alert on any suspicious outbound connections originating from the Apex One server.
Compensating Controls: If patching cannot be performed immediately, restrict network access to the Apex One management console at the network perimeter. Use a firewall to ensure that the console is only accessible from a limited set of trusted IP addresses belonging to security administrators. A Web Application Firewall (WAF) can also be deployed to inspect traffic and block malicious file upload attempts.
Exploitation status
Public Exploit Available: false
Analyst recommendation
This vulnerability represents a critical and immediate risk to the organization. The ability for an unauthenticated attacker to remotely execute code on a core security server necessitates urgent action. We strongly recommend that organizations prioritize the deployment of the vendor-supplied patches for CVE-2025-54948 across all affected installations without delay. While it is not yet on the CISA KEV list, its characteristics make it a prime target for future exploitation, and organizations should assume it will be exploited soon.