dbcve.org
Binisoft Windows Firewall ControlApplication · Malwarebytes

CVE-2022-25150

HIGH · 7.8 CVSS v3.1 Published 2022-02-14
Fix available
A fix is available. Upgrade to 6.8.1.0 or later.
See remediation →
80/100
Remediation priority · High
Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
In Malwarebytes Binisoft Windows Firewall Control before 6.8.1.0, programs executed from the Tools tab can be used to escalate privileges.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

In Malwarebytes Binisoft Windows Firewall Control before version 6.8.1.0, the Tools tab functionality allows execution of programs that can be manipulated by low-privileged users to escalate privileges to administrator level. This is a local privilege escalation vulnerability in how the application launches external programs from its interface.

MitigationUpdate Malwarebytes Binisoft Windows Firewall Control to version 6.8.1.0 or later, which contains the fix for this privilege escalation vulnerability.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
Binisoft Windows Firewall ControlApplication
Affected:< 6.8.1.0

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Local
Complexity
Low
Privileges
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Verify if Binisoft Windows Firewall Control is installed
    Open Control Panel > Programs and Features, or run 'Get-ItemProperty HKLM:\Software\Microsoft\Windows\CurrentVersion\Uninstall\* | Select-Object DisplayName, DisplayVersion' in PowerShell to list installed programs and look for 'Windows Firewall Control' or 'Binisoft' entries
    Affected if The program appears in the installed programs list
  2. Determine the installed version
    Locate the installed version from the Programs and Features list, or check the executable properties at the installation path (typically C:\Program Files\Binisoft\Windows Firewall Control\wfc.exe), right-click the executable, select Properties, and view the Details tab for the Product Version
    Affected if The displayed version is below 6.8.1.0 (for example, 6.7.0.0, 6.6.0.0, etc.)
  3. Confirm the Tools tab exists and is accessible
    Launch the application (wfc.exe), navigate to the main interface and look for a 'Tools' or 'Tools tab' option in the navigation or menu bar
    Affected if The Tools tab is present and can be opened by a standard user account
  4. Check if low-privileged users can interact with the Tools functionality
    Run the application under a standard (non-admin) user account and attempt to access the Tools tab to see if it launches external programs or utilities
    Affected if A standard user can access the Tools feature and execute programs from it

You are affected if Binisoft Windows Firewall Control is installed with a version number lower than 6.8.1.0 and the Tools tab functionality is accessible to standard users on the system.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Upgrade available Upgrade to 6.8.1.0 or later
Fixed in 6.8.1.0
Interim mitigation

Update Malwarebytes Binisoft Windows Firewall Control to version 6.8.1.0 or later, which contains the fix for this privilege escalation vulnerability.

Recommended fix High confidence

6.8.1.0 or later

  1. Check the current version of Binisoft Windows Firewall Control (right-click the system tray icon and select 'About' or check in the main window)
  2. Navigate to the official Binisoft website (binisoft.org) or the Malwarebytes website to download the latest version
  3. Download version 6.8.1.0 or later of Windows Firewall Control
  4. Close the application if running
  5. Run the installer and follow the prompts to upgrade
  6. Restart the computer if prompted
  7. Verify the upgrade was successful by checking the version number again

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Binisoft Windows Firewall Control Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA1.0 h
10.0 hours of engineering $1,750
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,800.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2022-25150 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2022-25150 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data