CVE-2025-33027: Bandisoft Bandizip · Inclusion of Web Functionality from an Untrusted Source
Affects Bandisoft BandizipSource CVE Database V5
Not known to be exploited · CVSS 6.1 Medium.
Data as of 26 Oct 2026, 11:42 UTC
- EPSS
- 0.2% chance of exploitation in 30 days – higher than 21% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:NExploitation evidence
Disclosed: evidence found.
CVE published 15 Apr 2025
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.
What to do
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| Bandisoft Bandizip | Affected
| Fixed in– |
AI-suggested
European organizations should implement the following specific mitigations: 1) Monitor Bandisoft announcements and apply patches promptly once available to address CVE-2025-33027. 2) Enforce strict policies on handling archives from untrusted or unknown sources, including scanning all compressed files with updated antivirus and endpoint detection tools before extraction. 3) Educate users about the risks of opening archives from untrusted origins and the importance of heeding security warnings, even if MotW is bypassed. 4) Consider restricting Bandizip usage to trusted users or replacing it with archive tools that correctly propagate MotW attributes. 5) Implement application whitelisting and execution control policies to prevent unauthorized code execution from user directories where extracted files reside. 6) Employ network-level protections such as email filtering and web content filtering to reduce the delivery of malicious archives. 7) Use endpoint detection and response (EDR) solutions to detect suspicious behaviors related to archive extraction and code execution. These measures, combined with user awareness, will reduce the risk of exploitation beyond generic advice.
Description
In Bandisoft Bandizip through 7.37, there is a Mark-of-the-Web Bypass Vulnerability. This vulnerability allows attackers to bypass the Mark-of-the-Web protection mechanism on affected installations of Bandizip. User interaction is required to exploit this vulnerability in that the target must visit a malicious page or open a malicious file. The specific flaw exists within the handling of archived files. When extracting files from a crafted archive that bears the Mark-of-the-Web, Bandizip does not propagate the Mark-of-the-Web to the extracted files. An attacker can leverage this vulnerability to execute arbitrary code in the context of the current user. NOTE: this is disputed because Mark-of-the-Web propagation can increase risk via security-warning habituation, and because the intended control sphere for file-origin metadata (e.g., HostUrl in Zone.Identifier) may be narrower than that for reading the file's content.