CVE-2025-50325: BandiZip v.7.37 is affected by a Authentication Bypass Vulnerability.
BandiZip v.7.37 is affected by a Authentication Bypass Vulnerability. This vulnerability allows remote attackers to bypass the Mark-of-the-Web protection mechanism on affected installations of BandiZip
Security readout for executives and security teams
Plain-English summary
Bandizip 7.37 may fail to preserve Windows Mark-of-the-Web protections when handling attacker-supplied archives. This can reduce security warnings or controls applied to extracted files, increasing the chance that a user trusts unsafe content. The issue requires user interaction and is not described as directly compromising availability.
Executive priority
Treat this as a moderate-priority endpoint security issue. Prioritize teams receiving external archives, such as finance, recruitment, support, and operations. Accelerate remediation if Bandizip 7.37 is widespread or Mark-of-the-Web is an important control against downloaded content.
Technical view
CVE-2025-50325 is a protection-mechanism bypass classified as CWE-693. The CVSS 3.1 score is 5.4: network-accessible, low complexity, no privileges required, user interaction required, unchanged scope, and low confidentiality and integrity impact. The supplied record identifies Bandizip 7.37, although its structured affected-product fields are incomplete.
Likely exposure
Endpoints using Bandizip 7.37 to extract archives obtained from the internet are potentially exposed, particularly where Mark-of-the-Web influences warnings or execution controls. The supplied structured affected-product data lists vendor, product, and versions as unavailable, so broader version exposure cannot be established.
Exploitation context
A remote attacker would need a user to receive and process attacker-controlled archive content. Successful bypass could cause extracted content to lack expected Mark-of-the-Web protections. The source bundle does not establish active exploitation, and the CVE is not listed as a CISA KEV entry.
Researcher notes
The CVE description calls this authentication bypass, but the documented effect is specifically Mark-of-the-Web protection bypass. CWE-693 better reflects that mechanism. No fixed release, vendor advisory statement, technical root cause, or exploitation evidence is included in the supplied data; validate these points against current vendor guidance.
Mitigation direction
Inventory endpoints running Bandizip 7.37, prioritizing systems that routinely process internet-sourced archives.
Check Bandisoft’s release history and guidance for a corrected version, then upgrade as directed.
Until remediation is confirmed, limit handling of untrusted archives with affected installations.
Retain endpoint protection and application-control policies as compensating safeguards.
Validation and detection
Confirm installed Bandizip versions across managed endpoints.
Review Bandisoft’s release history for explicit CVE or Mark-of-the-Web correction details.
In an isolated environment, verify extracted internet-origin files retain expected Mark-of-the-Web metadata.
Confirm endpoint controls still warn about or restrict untrusted extracted content.
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Potential ATT&CK relevance
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
cwe · low confidence lookup
CWE-693: Exact CWE lookup
Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
The CVE wording references authentication or credential exposure, so valid-account and credential-access review may help. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
CWE-693 · source CWE mapping
Protection Mechanism Failure
Protection Mechanism Failure represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.