dbcve.org
Improper AuthenticationWeakness · CWE-287

CVE-2026-1368

HIGH · 7.5 CVSS v3.1 Published 2026-02-18
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
84/100
Remediation priority · High
Remotely reachable No privileges Zero-click

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 · unedited
The Video Conferencing with Zoom WordPress plugin before 4.6.6 contains an AJAX handler that has its nonce verification commented out, allowing unauthenticated attackers to generate valid Zoom SDK signatures for any meeting ID and retrieve the site's Zoom SDK key.

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 confidence

The Video Conferencing with Zoom WordPress plugin before 4.6.6 has an AJAX handler with commented-out nonce verification, allowing unauthenticated attackers to retrieve the site's Zoom SDK key and generate valid Zoom SDK signatures for any meeting ID. This broken authentication allows complete bypass of the intended access controls.

MitigationUpgrade the Video Conferencing with Zoom plugin to version 4.6.6 or later, which includes proper nonce verification. Until then, consider restricting access to the affected AJAX endpoint via server-side configuration or disabling the plugin if immediate patching is not possible.

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
High
Integrity
None
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/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 checks

Work through these to decide whether this CVE applies to you.

  1. Verify plugin is installed
    In WordPress admin, go to Plugins > Installed Plugins and look for 'Video Conferencing with Zoom', or inspect the plugin directory at wp-content/plugins/video-conferencing-zoom/ for existence
    Affected if The plugin directory does not exist or the plugin is not listed in WordPress
  2. Check installed version
    In WordPress admin, go to Plugins > Installed Plugins and find the version number listed under the Video Conferencing with Zoom plugin name, or check the 'Version' header in wp-content/plugins/video-conferencing-zoom/video-conferencing-zoom.php
    Affected if Version is present and is lower than 4.6.6 (e.g., 4.6.5, 4.6.4, etc.)
  3. Inspect AJAX endpoint accessibility
    Check if the file wp-admin/admin-ajax.php responds to the zoom plugin's AJAX actions - look for the action parameter value that handles Zoom API key retrieval and signature generation (typically actions like 'zoom_api_key' or 'get_signature')
    Affected if The AJAX endpoint is publicly accessible without authentication and responds to Zoom-related action parameters
  4. Verify commented nonce code
    Examine the PHP file handling the AJAX request in the plugin (likely in includes/ or a handler file) for the presence of commented-out or missing wp_verify_nonce() or check_ajax_referer() calls
    Affected if The nonce verification code is commented out, missing, or conditionally disabled in the AJAX handler

The environment is affected if the Video Conferencing with Zoom plugin is installed with a version lower than 4.6.6 and the AJAX endpoint handling Zoom API key retrieval is accessible without authentication.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Upgrade the Video Conferencing with Zoom plugin to version 4.6.6 or later, which includes proper nonce verification. Until then, consider restricting access to the affected AJAX endpoint via server-side configuration or disabling the plugin if immediate patching is not possible.

Recommended fix High confidence

Video Conferencing with Zoom plugin version 4.6.6

  1. 1. Backup your WordPress database and files before making any changes
  2. 2. Navigate to Plugins > Installed Plugins in your WordPress admin dashboard
  3. 3. Find 'Video Conferencing with Zoom' in the plugin list
  4. 4. If an update is available, click 'Update Now' to upgrade to version 4.6.6 or later
  5. 5. Alternatively, you can manually upload the updated plugin files via Plugins > Add New > Upload Plugin
  6. 6. After updating, verify the nonce verification code is now properly implemented in the AJAX handler
  7. 7. Test that the Zoom integration still works correctly with your meetings

Generated from the published advisory — verify against the referenced sources before acting.

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation2.0 h
  • Testing2.0 h
  • Review / QA1.0 h
7.0 hours of engineering $1,240
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,984.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-1368 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-1368 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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