CVE-2025-50327: An issue in Franco Corbelli ZPAQFRANZ v.61.3 and before allows a remote attacker to escalate privileges and...
An issue in Franco Corbelli ZPAQFRANZ v.61.3 and before allows a remote attacker to escalate privileges and execute arbitrary code via a bypass of the Mark-of-the-Web protection mechanism
Security readout for executives and security teams
Plain-English summary
ZPAQFRANZ version 61.3 and earlier may let malicious content bypass Windows Mark-of-the-Web protections. If a user interacts with affected content, an attacker could reportedly run arbitrary code and gain elevated privileges, potentially compromising the system and its data.
Executive priority
Prioritize prompt inventory and remediation because successful exploitation could enable full system compromise. Focus first on internet-facing workflows and employees who routinely receive untrusted files. Emergency response is not substantiated by active-exploitation evidence, but the potential impact and low-complexity rating justify expedited handling.
Technical view
CVE-2025-50327 is classified as CWE-693, failure of a protection mechanism. The reported Mark-of-the-Web bypass affects ZPAQFRANZ 61.3 and earlier. CVSS 3.1 rates it 8.8: network-accessible, low complexity, no prior privileges, user interaction required, with high confidentiality, integrity, and availability impact.
Likely exposure
Exposure is most likely on Windows systems running ZPAQFRANZ 61.3 or earlier where users handle attacker-supplied or untrusted content. The supplied record does not identify CPEs, deployment prevalence, or affected operating-system versions, so organizations should confirm installations and workflows directly.
Exploitation context
The supplied sources do not establish active exploitation, and the CVE is not listed as KEV in the provided bundle. Exploitation reportedly requires user interaction, but no prior attacker privileges and low attack complexity are reflected in the CVSS vector. No exploit procedure is provided here.
Researcher notes
The public record is incomplete: structured affected-product fields and CPEs are unavailable, while the narrative names ZPAQFRANZ 61.3 and earlier. The supplied bundle does not identify a fixed release, detailed root cause, operating-system scope, or confirmed exploitation. Treat version and remediation conclusions beyond the narrative as unverified.
Mitigation direction
Inventory ZPAQFRANZ installations and identify versions 61.3 or earlier.
Check the vendor release page for current remediation or upgrade guidance.
Restrict processing of untrusted content with affected versions until remediation is confirmed.
Use endpoint controls and least privilege to limit arbitrary-code impact.
Validation and detection
Confirm installed ZPAQFRANZ versions on potentially exposed Windows endpoints.
Review vendor releases to determine whether a fixed version is available.
Identify users and systems that process externally supplied content with ZPAQFRANZ.
Review endpoint telemetry for unusual child processes or privilege changes associated with ZPAQFRANZ.
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 code or command execution, so execution technique review may help defensive triage. 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.
1CVSS vectors
3Timeline events
1ADP providers
3Source links
SSVC decision data
CISA-ADPCISA Coordinator
Timestamp
Version
2.0.3
Exploitation: noneAutomatable: noTechnical Impact: total
CVSS vector scores
1 official score
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.