CVE-2025-62482
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 · uneditedCross-site scripting in Zoom Workplace for Windows before version 6.5.10 may allow an unauthenticated user to impact integrity 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 · moderate confidenceCross-site scripting (XSS) vulnerability in Zoom Workplace for Windows versions prior to 6.5.10 allows unauthenticated attackers to inject malicious scripts via network access, potentially compromising the integrity of user sessions when the vulnerable client renders malicious content.
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.5.10< 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
- Changed
- Confidentiality
- Low
- Integrity
- Low
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/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 Zoom Workplace Desktop version on WindowsOpen Zoom desktop client, click Help > About Zoom, or open Windows Settings > Apps > Installed Apps and locate Zoom Workplace to view the version numberAffected if Version number displayed is lower than 6.5.10
-
Verify Zoom process is the Windows desktop clientOpen Task Manager, look for Zoom.exe process running, confirm it is the Zoom Workplace desktop client (not the web or mobile versions)Affected if Zoom Workplace Desktop for Windows is running and version is below 6.5.10
-
Check Zoom Meeting SDK version if installed as dependencyFor systems with Zoom Meeting SDK installed, check the SDK DLL files or version manifest in the installation directory (typically in Program Files or application-specific folders)Affected if Zoom Meeting SDK version is present and below 6.5.10
Your environment is affected if Zoom Workplace Desktop for Windows or Zoom Meeting SDK is installed with a version number lower than 6.5.10, as this is the specific version threshold for this XSS vulnerability.
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.5.10
Upgrade Zoom Workplace for Windows to version 6.5.10 or later to remediate this vulnerability. Organizations should deploy the update through standard software distribution channels.
6.5.10
- Identify all Zoom Workplace Desktop installations on Windows that are running a version prior to 6.5.10
- Identify all deployments using Meeting Software Development Kit versions prior to 6.5.10
- Download Zoom Workplace Desktop version 6.5.10 or later from the official Zoom website (www.zoom.com) or your organization's software distribution channel
- Apply the update to all affected Zoom Workplace Desktop installations
- Update any applications using the Meeting Software Development Kit to version 6.5.10 or later
- Verify that the updated versions are running correctly and the XSS vulnerability is remediated
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation4.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 $2,560.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-62482 — 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-62482 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