CVE-2025-27442
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 some Zoom Workplace Apps may allow an unauthenticated user to conduct a loss of integrity via adjacent 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 confidenceThis is a cross-site scripting (XSS) vulnerability in certain Zoom Workplace Applications that allows an unauthenticated attacker with adjacent network access to inject malicious scripts, compromising the integrity of user sessions or data.
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.10< 6.3.0< 6.3.10< 6.4.0< 6.4.0< 6.3.10< 6.1.16>= 6.1.17, < 6.2.12CVSS 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
- Adjacent
- Complexity
- Low
- Privileges
- None
- User interaction
- Required
- Scope
- Changed
- Confidentiality
- Low
- Integrity
- Low
- Availability
- None
CVSS:3.1/AV:A/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.
-
Identify installed Zoom productOpen the Zoom application, click your profile picture or initials in the top right, then look for 'About Zoom' or 'Check for Updates' to see which Zoom product is installed (Zoom Workplace Desktop, Zoom Rooms, Zoom Rooms Controller, or Zoom Workplace VDI)Affected if Any Zoom product from the affected list is installed
-
Determine installed version numberIn the Zoom app, go to Help > About (or the About section) to view the exact version number displayed (for Zoom Rooms, check the controller or room display system information)Affected if The version shown does not match or is lower than the fixed versions (6.3.10 for Desktop/Workplace/SDK, 6.4.0 for Rooms/Controller, 6.1.16 or 6.2.12 for VDI depending on branch)
-
Compare against affected version rangesReference the specific range for your product: Desktop/Workplace/SDK < 6.3.10, Rooms/Controller < 6.4.0, VDI < 6.1.16 or >= 6.1.17 and < 6.2.12. If your version falls within any of these ranges, you are potentially affectedAffected if Your installed version falls within any of the vulnerable ranges listed
-
Verify web interface exposureCheck if Zoom Workplace web portals, Zoom Web SDK, or browser-based meeting interfaces are in use on your network, as XSS requires web-based input/output to be exploitableAffected if Web-facing Zoom interfaces are accessible and your version is vulnerable
You are affected if you have any Zoom product from the affected list running a version lower than 6.3.10 (Desktop/Workplace/SDK), 6.4.0 (Rooms/Controller), or the VDI ranges, especially if web interfaces are exposed to adjacent network users.
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.1.166.2.126.3.0
Apply Zoom's available patches for affected Workplace Apps and implement output encoding/context-aware sanitization for user-supplied data in web interfaces.
Upgrade to: Workplace Desktop 6.3.10, Meeting SDK 6.3.10, Rooms 6.4.0, Rooms Controller 6.4.0, Workplace 6.3.10, or Workplace VDI 6.1.16/6.2.12 as applicable
- Identify which Zoom product(s) from the affected list are deployed in your environment
- Access the Zoom Download Center (zoom.us/download) or your Zoom admin portal
- Download the appropriate fixed version for your product: Workplace Desktop 6.3.10, Meeting SDK 6.3.10, Rooms 6.4.0, Rooms Controller 6.4.0, Workplace App 6.3.10, or Workplace VDI 6.1.16+/6.2.12+
- Follow standard Zoom upgrade procedures for your deployment method (MSI/PPKG for managed deployments, direct download for end-users)
- Restart the Zoom service/components after upgrade
- Verify the installed version matches the fixed release
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation8.0 h
- Testing6.0 h
- Review / QA3.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,248.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-27442 — 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-27442 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