CVE-2025-46786
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 authenticated user to impact app 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 Apps allows authenticated users to inject malicious scripts that could compromise application integrity. The attack is exploitable over the network and requires valid authentication credentials, targeting the integrity aspect of the application rather than confidentiality or availability.
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.4.0< 6.4.0< 6.4.0< 6.4.0< 6.4.0< 6.1.17>= 6.1.18, < 6.2.13>= 6.2.14, < 6.3.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.
-
Identify installed Zoom productOpen Zoom application, go to Help > About Zoom, or check the installed programs list in the system control panel to determine which Zoom product is installed (Workplace Desktop, Rooms, Rooms Controller, VDI, or Meeting SDK)Affected if Any Zoom product from the affected product list is installed
-
Check Zoom Workplace Desktop versionOpen Zoom Desktop app, click your profile picture or Help menu, then select About Zoom. Note the version number displayed (e.g., 6.3.10)Affected if Version is below 6.4.0 (e.g., 6.3.x, 6.2.x, etc.)
-
Check Zoom Rooms or Rooms Controller versionOpen Zoom Rooms application, navigate to Settings or About section, or check the version displayed on the Rooms controller deviceAffected if Version is below 6.4.0
-
Check Zoom Workplace VDI versionConsult your system administrator or check the VDI image/package version information as displayed in the virtual desktop environmentAffected if Version is below 6.1.17, OR between 6.1.18 and 6.2.12, OR between 6.2.14 and 6.3.9
-
Confirm application handles user contentVerify that the Zoom application is used for communication features such as chat, meeting messages, or file sharing where other authenticated users can send contentAffected if The application processes content from other users (required for XSS to be exploitable)
You are affected if you have any Zoom product installed with a version number that falls within the ranges specified: below 6.4.0 for most products, or within the specific VDI ranges below 6.3.10, and you use features that process content from other authenticated 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.176.2.136.3.10
Apply vendor patches when released by Zoom; as a defensive measure, implement Content Security Policy (CSP) headers and ensure users are aware of risks from clicking untrusted links within the application until the fix is available.
Upgrade to Zoom Workplace version 6.4.0 or later (or VDI versions 6.1.17+, 6.2.13+, 6.3.10+ respectively)
- 1. Save any active meeting or session data and close the Zoom application
- 2. For Workplace Desktop, Meeting SDK, Rooms, Rooms Controller, and Workplace apps: Navigate to zoom.us/download or use your system's software update mechanism to download version 6.4.0 or later
- 3. For Workplace Virtual Desktop Infrastructure: Update your VDI environment to version 6.1.17 or higher, 6.2.13 or higher, or 6.3.10 or higher (recommended: 6.4.0 or later)
- 4. Run the installer with administrator privileges
- 5. Restart the application and verify the version number reflects 6.4.0 or higher in the Help > About section
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation1.0 h
- Implementation2.0 h
- Testing1.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,424.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-46786 — 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-46786 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