CVE-2025-44090
8.8OhSoft · CoffeeZip
OhSoft CoffeeZip version 4.8.0.0 contains a vulnerability that allows unauthenticated attackers to execute arbitrary code by enticing a user to download and open a maliciously crafted archive file.
Executive summary
A critical remote code execution vulnerability in OhSoft CoffeeZip 4.8.0.0 poses a severe risk to system integrity and security.
Vulnerability
This vulnerability involves an arbitrary code execution flaw triggered when an unauthenticated attacker provides a crafted archive file to a user. The application fails to properly validate the contents of the archive, resulting in unauthorized command execution upon user interaction.
Business impact
The ability for an attacker to execute arbitrary code on a victim's machine can lead to a total compromise of the affected host. This may result in unauthorized data exfiltration, the installation of persistent malware, or lateral movement within the corporate network. With a CVSS score of 8.8, this flaw represents a high risk to organizational security posture.
Remediation
Immediate Action: Users should immediately stop using CoffeeZip version 4.8.0.0 and uninstall the software until a security patch is provided by the vendor.
Proactive Monitoring: Security teams should monitor endpoint logs for suspicious child processes spawned by archive management applications and unexpected network connections.
Compensating Controls: Deploy endpoint detection and response tools to identify and block the execution of unauthorized binaries or scripts originating from archive extraction utilities.
Exploitation status
Public Exploit Available: Yes, a published proof-of-concept exists, attributed to the research write-up at the provided GitHub reference.
Analyst recommendation
Given the potential for remote code execution, this vulnerability must be treated with high priority. Organizations should enforce strict software control policies and ensure users are aware of the risks associated with opening untrusted archive files. Immediate removal of the affected version is the only effective way to eliminate this risk until the vendor releases a verified security update.