CVE-2026-6964
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 · uneditedThe Video Conferencing with Zoom plugin for WordPress is vulnerable to authorization bypass in all versions up to, and including, 4.6.7. This is due to the plugin not properly verifying that a user is authorized to perform an action. This makes it possible for unauthenticated attackers to obtain the site's Zoom SDK API key and a freshly-signed JWT that can be used with the Zoom Web SDK to join any Zoom meeting associated with those credentials without a legitimate invitation.
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 confidenceThe Video Conferencing with Zoom WordPress plugin versions up to 4.6.7 contains an authorization bypass vulnerability allowing unauthenticated attackers to retrieve the site's Zoom SDK API key and a freshly-signed JWT. These credentials can then be used to join any Zoom meeting associated with those credentials without authorization.
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
- Network
- Complexity
- Low
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- Low
- Integrity
- None
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/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.
-
Identify if the Video Conferencing with Zoom plugin is installedIn the WordPress admin dashboard, navigate to Plugins > Installed Plugins and look for 'Video Conferencing with Zoom' in the list of active pluginsAffected if The plugin is present in the WordPress installation
-
Determine the installed plugin versionClick on the plugin name in the Plugins list to view the version number, or inspect the plugin header in wp-content/plugins/video-conferencing-zoom/main.php for the 'Version' commentAffected if The version is 4.6.7 or any earlier version (the vulnerability affects versions up to and including 4.6.7)
-
Check if Zoom API credentials are configuredNavigate to Zoom > API Settings in the WordPress admin panel and examine whether a Zoom SDK API Key and API Secret are populated and savedAffected if The plugin has valid Zoom SDK API credentials configured - the vulnerability allows retrieval of these credentials when they exist
-
Test unauthenticated access to credential retrieval endpointMake a GET request to the site's /wp-json/video-conferencing-zoom/v1/credentials endpoint (or similar unauthenticated API endpoint) without providing any authentication tokensAffected if The endpoint returns Zoom API key and a signed JWT without requiring authentication - this confirms the vulnerability is present and exploitable
A user is affected if they have Video Conferencing with Zoom plugin version 4.6.7 or earlier installed with Zoom API credentials configured, and the vulnerable unauthenticated endpoint is accessible.
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.
From vendor dataUpdate the Video Conferencing with Zoom plugin to the latest version once available. As a precautionary measure, consider rotating the Zoom SDK API key and reviewing access logs for unauthorized meeting joins.
- 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-2026-6964 — 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-2026-6964 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