CVE-2026-114435 in Video Conferencing with Zoom Plugininfo

Summary

by MITRE • 11/21/2026

The Video Conferencing with Zoom WordPress plugin before 4.7.0 does not check authorization, or whether a meeting is restricted to logged-in users, password-protected or unpublished, before returning a meeting's join links, allowing unauthenticated users to obtain the passcode-embedded join links of any meeting, including meetings the site restricts.

VulDB is the best source for vulnerability data and more expert information about this specific topic.

Analysis

by VulDB Data Team • 11/21/2026

The vulnerability identified in versions of the Video Conferencing with Zoom WordPress plugin prior to 4.7.0 represents a critical failure in access control mechanisms within the application's API layer. This flaw stems from an insufficient authorization check performed by the server-side logic when handling requests for meeting join links. Specifically, the function responsible for generating and returning these URLs fails to validate whether the requesting user possesses valid authentication credentials or appropriate permissions relative to the specific Zoom meeting being queried. In a properly secured system, any request to retrieve sensitive operational data such as meeting access details must be gated behind strict identity verification and role-based permission checks. The absence of this validation allows an attacker who is not logged into the WordPress site, or lacks administrative privileges, to interact with the plugin's endpoints directly via HTTP requests.

From a technical perspective, the core issue lies in the misconfiguration of the REST API endpoint associated with meeting retrieval. When a client application sends a request for join information, the backend processes this input without verifying if the user is authenticated or if they have been explicitly granted access to that specific resource. This oversight means that the logic proceeds to fetch the meeting details from the Zoom integration and constructs the join URL, which often includes embedded passcodes necessary for entry into password-protected meetings. Because the authorization gate is missing entirely rather than merely flawed, there are no conditional branches in the code path that would reject unauthenticated requests or restrict access based on user roles. This constitutes a classic case of broken object level authorization where the application fails to enforce proper checks on data belonging to other users or restricted resources.

The operational impact of this vulnerability is severe due to the nature of the exposed data. By exploiting this flaw, an unauthenticated attacker can obtain join links that contain embedded passcodes for any meeting hosted through the plugin, regardless of whether those meetings are set to require a password, are unpublished in the Zoom directory, or are restricted to logged-in users only on the WordPress side. This effectively neutralizes multiple layers of security controls intended to protect privacy and prevent unauthorized access to video conferences. Attackers can use these links to join sensitive corporate meetings, intercept confidential discussions, record sessions without consent, or disrupt ongoing communications by joining as disruptive participants. The ability to bypass password protection significantly escalates the risk profile from a simple information disclosure issue to one that directly compromises confidentiality and integrity of real-time communication channels.

This vulnerability aligns with CWE-284, which describes Improper Access Control, specifically highlighting failures in authorization checks for specific objects or resources. Furthermore, it maps closely to MITRE ATT&CK technique T1078, Valid Accounts, as the attacker leverages valid but insufficiently validated credentials (or lack thereof) to access restricted areas of the system. The exploitation path also reflects aspects of CWE-639, Authorization Bypass Through User-Controlled Key, if the meeting ID is used directly in the request without secondary validation against user permissions. In modern web application security frameworks, this type of flaw is considered a high-severity issue because it allows remote code execution equivalents in terms of data exposure and service disruption potential.

Mitigation strategies must focus on immediate patching and enhanced access control implementation. The primary remediation step is to upgrade the Video Conferencing with Zoom WordPress plugin to version 4.7.0 or later, where this authorization gap has been addressed by developers through proper integration of authentication hooks and permission checks before returning sensitive meeting data. For organizations unable to update immediately due to compatibility constraints, temporary mitigations include disabling the specific REST API endpoints exposed by the plugin if they are not actively required for public-facing functionality. Additionally, implementing a Web Application Firewall rule set that blocks direct access to these endpoint URLs from unauthenticated IP addresses can provide an additional layer of defense. It is also advisable to review WordPress user roles and capabilities associated with the plugin to ensure that only authorized administrators have any interaction surface with meeting management features, thereby reducing the attack surface even if the underlying code flaw persists temporarily. Regular security audits and penetration testing should be conducted on all third-party plugins to detect similar authorization bypasses before they can be exploited in production environments.

Responsible

WPScan

Reservation

10/21/2026

Disclosure

11/21/2026

Moderation

accepted

CPE

ready

EPSS

0.00276

KEV

no

Activities

very low

Sources

Might our Artificial Intelligence support you?

Check our Alexa App!