dbcve.org
Command InjectionWeakness · CWE-77

CVE-2025-1910

MEDIUM · 6.3 CVSS v4.0 Published 2025-12-04
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
65/100
Remediation priority · Elevated
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
The WatchGuard Mobile VPN with SSL Client on Windows allows a locally authenticated non-administrative Windows user to escalate their privileges to NT AUTHORITY/SYSTEM on the Windows machine where the VPN Client is installed.

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

A local privilege escalation vulnerability in WatchGuard Mobile VPN with SSL Client 12.0-12.11.2 for Windows allows an authenticated non-administrative user to gain NT AUTHORITY/SYSTEM privileges, likely through improper privilege handling in the VPN client service or driver.

MitigationApply the vendor-supplied patch/update to Mobile VPN with SSL Client to address the privilege escalation flaw; ensure non-admin users cannot manipulate VPN client components.

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

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
Authentication
X
User interaction
None
Scope
X

CVSS:4.0/AV:L/AC:L/AT:N/PR:L/UI:N/VC:N/VI:N/VA:N/SC:H/SI:H/SA:H/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X

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 WatchGuard Mobile VPN with SSL Client is installed
    Open Programs and Features (appwiz.cpl) or check C:\Program Files\WatchGuard\ for the Mobile VPN with SSL Client directory
    Affected if The software is present on the system
  2. Determine the installed version number
    Right-click the Mobile VPN with SSL Client application, select Properties, then go to the Details tab to view the Product Version, or run 'Get-ItemProperty' on the installation directory for version info
    Affected if The installed version falls within 12.0 through 12.11.2 (inclusive)
  3. Confirm the Mobile VPN service is running
    Open Services (services.msc) and locate the WatchGuard Mobile VPN service, or run 'Get-Service | Where-Object {$_.DisplayName -like "*WatchGuard*"}' in PowerShell
    Affected if The service exists and is in a Running state
  4. Check for non-administrative user access to VPN client components
    Inspect file and registry permissions on the VPN client installation directory and service binary using icacls or Registry Editor to verify if standard users have write access to privileged locations
    Affected if Non-admin users have modify or write permissions to service binaries, configuration files, or driver files

A system is affected if WatchGuard Mobile VPN with SSL Client version 12.0 through 12.11.2 is installed with the service running and non-admin users can manipulate client components.

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
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Apply the vendor-supplied patch/update to Mobile VPN with SSL Client to address the privilege escalation flaw; ensure non-admin users cannot manipulate VPN client components.

Recommended fix Moderate confidence

Mobile VPN with SSL Client version higher than 12.11.2 (check WatchGuard for exact latest stable release)

  1. Check the current installed version of WatchGuard Mobile VPN with SSL Client by opening the application and navigating to Help > About, or by running 'wgm vpn' from command prompt
  2. Identify if the installed version is 12.0 through 12.11.2 inclusive, as these versions are affected by CVE-2025-1910
  3. Visit the official WatchGuard support portal at www.watchguard.com to download the latest version of Mobile VPN with SSL Client
  4. Download and install the latest version of Mobile VPN with SSL Client (version higher than 12.11.2)
  5. Verify the installation was successful and confirm the new version number post-installation
  6. Restart the Windows machine to ensure all components are properly loaded

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

Have this fixed Scoped from the published advisory
  • Consultation4.0 h
  • Implementation6.0 h
  • Testing4.0 h
  • Review / QA2.0 h
16.0 hours of engineering $2,840
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-1910 — 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-2025-1910 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