CVE-2025-30662
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 · uneditedSymlink following in the installer for the Zoom Workplace VDI Plugin macOS Universal installer before version 6.3.14, 6.4.14, and 6.5.10 in their respective tracks may allow an authenticated user to conduct a disclosure of information via network access.
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 confidenceThis is a symlink following vulnerability in the Zoom Workplace VDI Plugin macOS Universal installer. The vulnerability allows an authenticated local user to manipulate symlinks during the installation process to cause the installer to read or write files outside the intended installation directory, leading to unauthorized information disclosure.
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< 6.3.14>= 6.4.0, < 6.4.14>= 6.5.0, < 6.5.10CVSS 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
- Network
- Complexity
- Low
- Privileges
- None
- User interaction
- Required
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- None
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:N/A:N
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 checksWork through these to decide whether this CVE applies to you.
-
Check if Zoom VDI Plugin is installedLook for the Zoom VDI Plugin application on the system. On macOS, check /Applications/ folder for 'Zoom Workplace VDI Plugin' or similar VDI-related Zoom packages. You can also run: ls /Applications/ | grep -i zoomAffected if The Zoom VDI Plugin application is present on the system
-
Identify the installed Zoom VDI Plugin versionRight-click the Zoom VDI Plugin app, select 'Get Info', and note the version number displayed. Alternatively, run: defaults read /Applications/Zoom\ Workplace\ VDI\ Plugin.app/Contents/Info CFBundleShortVersionString (adjust path if different)Affected if The version number is less than 6.3.14, OR between 6.4.0 and 6.4.13 inclusive, OR between 6.5.0 and 6.5.9 inclusive
-
Confirm this is the macOS Universal installer variantCheck the app bundle architecture or installer package type. Run: file /Applications/Zoom\ Workplace\ VDI\ Plugin.app/Contents/MacOS/Zoom\ Workplace\ VDI\ Plugin (or inspect the app bundle for Universal binary indicators)Affected if The application is a Universal binary (containing both Intel and Apple Silicon code) and is the VDI-specific installer variant
-
Verify the installation was performed using the VDI plugin installerCheck installation receipts or logs for evidence that the VDI-specific installer was used. Inspect /Library/Receipts or the installer history: pkgutil -- receipts | grep -i vdiAffected if VDI-specific installation records are found in system receipts
You are affected if the Zoom Workplace VDI Plugin for macOS is installed and its version falls within any of the vulnerable ranges: below 6.3.14, 6.4.0-6.4.13, or 6.5.0-6.5.9.
Generated from the published advisory. Verify against your own configuration.
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 · scoped6.3.146.4.146.5.10
Update Zoom Workplace VDI Plugin to version 6.3.14 (or later 6.3.x), 6.4.14 (or later 6.4.x), or 6.5.10 (or later 6.5.x) depending on the track in use. Prior to updating, ensure the installer is sourced from a trusted channel.
Upgrade to version 6.3.14 (6.3.x track), 6.4.14 (6.4.x track), or 6.5.10 (6.5.x track)
- Identify which track (6.3.x, 6.4.x, or 6.5.x) of the Zoom Workplace VDI Plugin macOS Universal installer is currently in use
- Obtain the appropriate fixed version from Zoom's official website or internal IT distribution system: version 6.3.14 for the 6.3.x track, version 6.4.14 for the 6.4.x track, or version 6.5.10 for the 6.5.x track
- Uninstall the current version of the Zoom Workplace VDI Plugin following standard macOS application removal procedures
- Install the corresponding fixed version (6.3.14, 6.4.14, or 6.5.10) by running the updated installer package
- Verify the installed version matches the expected fixed release
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation1.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,696.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-30662 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2025-30662 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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