Here are the CVE updates for the week of August 18th through the 24th.
🔴 Critical Severity Vulnerabilities
Trend Micro Apex One OS Command Injection Vulnerability (CISA KEV) | CVE-2025-54948
Description:
A critical vulnerability affects Trend Micro Apex One (on-premise) management console, which allows a pre-authenticated remote attacker to exploit the system. Specifically, the flaw enables attackers to upload malicious code to the server and then execute arbitrary commands with the privileges of the management console. Moreover, because exploitation requires no valid credentials, organizations face a severe risk if they rely on Apex One for endpoint protection.
Potential Impacts:
- Remote Code Execution (RCE): Attackers can take full control of the affected server.
- Malware Deployment: Consequently, the flaw could be used to install ransomware, backdoors, or spyware.
- Privilege Escalation: Furthermore, compromised systems may allow attackers to move laterally across the network.
- Data Breach: Sensitive endpoint and security-related data stored in the console may become exposed.
- Business Disruption: As a result, attackers could disable security policies or services, leaving endpoints unprotected.
Mitigation Recommendations:
- Apply Security Patches: Update Trend Micro Apex One to the latest fixed version as released by Trend Micro.
- Restrict Console Access: Therefore, limit network exposure of the Apex One management console to trusted administrators only.
- Implement Web Application Firewall (WAF): In addition, use a WAF to help block malicious payloads attempting to exploit the flaw.
- Monitor System Logs: Enable logging and consistently monitor for unusual file uploads or command executions.
- Incident Response Preparedness: Ensure response teams remain ready to act in case of exploitation, including isolating the affected system.
Sandbox Escape via Incorrect Handle in Mojo (Google Chrome on Windows) | CVE-2025-4609
Description:
A sandbox escape vulnerability impacts Google Chrome on Windows because of incorrect handle management in Mojo IPC under specific conditions. The flaw exists in Chrome versions prior to 136.0.7103.113, where improper handling of object references allows an attacker to leverage a malicious file and escape the browser sandbox. Since the Chrome sandbox functions as a critical security boundary, successful exploitation can consequently enable attackers to execute code with higher privileges than intended.
Potential Impacts:
- Sandbox Escape: Attackers can bypass Chrome’s built-in sandbox restrictions.
- Privilege Escalation: Once outside the sandbox, they may gain higher-level access on the operating system.
- Arbitrary Code Execution: Moreover, malicious files can allow attackers to execute arbitrary code outside of Chrome’s restricted environment.
- Chained Exploits: Similarly, this flaw could be combined with other browser vulnerabilities (e.g., RCE in renderer process) for full system compromise.
Mitigation Recommendations:
- Update Chrome: Upgrade to version 136.0.7103.113 or later where this issue has been fixed.
- Enable Auto-Updates: In addition, ensure Chrome’s auto-update feature is enabled to receive patches promptly.
- Least Privilege Execution: Run Chrome with standard user accounts to reduce potential impact in case of compromise.
- OS Hardening: Therefore, apply Microsoft’s security updates and enable exploit mitigations (e.g., ASLR, DEP, CFG).
- Monitor for Exploits: Consequently, watch for suspicious file downloads or execution attempts from untrusted sources.
Authentication Bypass in zhisheng17 Blog | CVE-2024-50644
Description:
An authentication bypass vulnerability exists in zhisheng17 Blog version 3.0.1-SNAPSHOT, where API endpoints fail to properly enforce authentication. Attackers can directly exploit this flaw by accessing API endpoints without providing a valid token. Consequently, unauthorized users can interact with sensitive application functions and data that should remain restricted to authenticated sessions.
Potential Impacts:
- Unauthorized API Access: Attackers can invoke API calls meant for authenticated users.
- Sensitive Data Exposure: As a result, private user information, posts, or system details may be retrieved.
- Privilege Escalation: Furthermore, attackers may perform administrative or restricted operations without login.
- Service Abuse: Similarly, the API can be abused for data manipulation or mass extraction.
Mitigation Recommendations:
- Upgrade/Patch: Apply the latest patched version of zhisheng17 Blog once available.
- Enforce Token Validation: Therefore, ensure all API endpoints validate session tokens or API keys before granting access.
- Adopt Strong Authentication Frameworks: In addition, implement centralized frameworks (e.g., Spring Security) to manage access control.
- Audit and Monitor: Log all API calls and actively monitor for suspicious unauthenticated patterns.
- Implement Rate Limiting: Consequently, reduce the risk of automated abuse by restricting the number of unauthenticated requests.
Authentication Bypass in MallChat v1.0-SNAPSHOT | CVE-2024-50645
Description:
An authentication bypass vulnerability impacts MallChat v1.0-SNAPSHOT, where API endpoints can be accessed without requiring a valid token. This flaw allows unauthenticated attackers to directly interact with protected APIs, thereby bypassing intended authentication mechanisms. As a result, attackers may gain unauthorized access to sensitive data or perform actions reserved for authenticated users.
Potential Impacts:
- Unauthorized Data Access: Attackers may retrieve sensitive user information.
- Privilege Escalation: Moreover, APIs requiring elevated privileges could be abused without proper checks.
- Service Abuse: Consequently, attackers could send requests to manipulate application logic or disrupt operations.
- Data Integrity Risks: Malicious actors may alter or delete data through exposed API endpoints.
Mitigation Recommendations:
- Apply Security Patch: Update MallChat to the latest fixed version.
- Enforce Authentication Checks: Require tokens for every API request.
- Use API Gateway/WAF: Block unauthorized requests before they reach the backend.
- Enable Logging & Monitoring: Detect suspicious unauthenticated requests.
- Principle of Least Privilege: Limit API access rights.
🟠 High Severity Vulnerabilities
Apple iOS, iPadOS, and macOS Out-of-Bounds Write Vulnerability (CISA KEV) | CVE-2025-43300: A flaw in Apple’s image processing allows memory corruption when handling crafted images. Exploitation can lead to arbitrary code execution. Apple confirmed possible in-the-wild exploitation.
Incorrect Access Control in SpringBootBlog preHandle Function | CVE-2024-53494: SpringBootBlog v1.0.0 fails to enforce proper access control in preHandle. Attackers can access restricted components without authentication.
Directory Traversal in MindManager for Windows | CVE-2024-56179: Crafted .mmap files exploit directory traversal in versions prior to 24.1.150, allowing overwriting of critical files.
Arbitrary Code Execution via Malicious .maplet Files in Maple | CVE-2010-20120: Maple ≤13 executes commands embedded in .maplet files. Attackers can craft files to execute code when opened.
🟡 Medium Severity Vulnerabilities
Stored XSS in Liferay Portal & DXP | CVE-2025-43765: Malicious input in web content text field executes JavaScript in users’ browsers, compromising sessions and data.
Self-ReDoS in Kaleo Designer Portlet (Liferay Portal and DXP) | CVE-2025-43764: Unsafe regex in Role Name search allows authenticated users to freeze browsers with complex input.
XSS in NextChat HTMLPreview Component | CVE-2025-50733: Unsanitized AI-generated HTML in iframes allows attackers to inject scripts into users’ browsers.
XSS in IBM QRadar SIEM Dashboard | CVE-2025-36042: Authenticated attackers can inject JavaScript into dashboards, hijacking sessions and altering UI behavior.