CVE-2026-1368VulnerabilityPublished 18 Feb 2026

CVE-2026-1368: Video Conferencing with Zoom (WordPress plugin) · Improper Authentication

Affects Video Conferencing with Zoom (WordPress plugin)Source CVE Database V5

Not known to be exploited · public detection template (Nuclei) · CVSS 7.5 High : upgrade to 4.6.6 soon.

Data as of 25 Oct 2026, 19:02 UTC

CVSS 3.1 base score

7.5High

How severe the flaw is on the 0–10 CVSS scale.

EPSS: 1.3% chance of exploitation in 30 days – higher than 70% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch: Available – fixed in 4.6.6

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N

Attack Vector: Network
Attack Complexity: Low
Privileges Required: None
User Interaction: None
Scope: Unchanged
Confidentiality: High
Integrity: None
Availability: None

Bold values are the worst case: easiest to exploit or largest impact.

Attack Vector: Network: The vulnerable component is bound to the network stack and the set of possible attackers extends beyond the other options listed, up to and including the entire Internet. Such a vulnerability is often termed 'remotely exploitable' and can be thought of as an attack being exploitable at the protocol level one or more network hops away (e.g., across one or more routers).
Attack Complexity: Low: Specialized access conditions or extenuating circumstances do not exist. An attacker can expect repeatable success against the vulnerable component.
Privileges Required: None: The attacker is unauthorized prior to attack, and therefore does not require any access to settings or files to carry out an attack.
User Interaction: None: The vulnerable system can be exploited without any interaction from any user.
Scope: Unchanged: An exploited vulnerability can only affect resources managed by the same security authority. In this case, the vulnerable component and the impacted component are either the same, or both are managed by the same security authority.
Confidentiality: High: There is total loss of confidentiality, resulting in all resources within the impacted component being divulged to the attacker. Alternatively, access to only some restricted information is obtained, but the disclosed information presents a direct, serious impact.
Integrity: None: There is no loss of integrity within the impacted component.
Availability: None: There is no impact to availability within the impacted component.

Definitions: FIRST CVSS v3.1 specification.

Exploitation evidence

Disclosed: evidence found.
CVE published 18 Feb 2026
Detectable: evidence found.
nuclei template: Video Conferencing with Zoom API < 4.6.6 - Unauthenticated SDK Signature Generation
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 2026-10-25.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponised: Public exploit code exists in Metasploit or Exploit-DB, or CISA SSVC reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

What to do

Upgrade Video Conferencing with Zoom (WordPress plugin) to 4.6.6.

Affected software

Product	Affected	Fixed in
Video Conferencing with Zoom	Affected <4.6.6	Fixed in 4.6.6

AI-suggested

Immediate mitigation involves updating the Video Conferencing with Zoom WordPress plugin to version 4.6.6 or later, where nonce verification is restored. If an update is not yet available, site administrators should implement custom nonce verification in the AJAX handler to ensure only authenticated requests can generate Zoom SDK signatures. Restricting access to the AJAX endpoint via web application firewall (WAF) rules or IP whitelisting can reduce exposure. Monitoring logs for unusual AJAX requests related to Zoom SDK signature generation can help detect exploitation attempts. Organizations should also rotate Zoom SDK keys if compromise is suspected. Educating site administrators on the importance of timely plugin updates and secure coding practices is critical. Finally, consider isolating Zoom integration components and limiting their permissions to minimize impact if compromised.

Description

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.

Impact

For European organizations, this vulnerability could lead to unauthorized access to internal or external video conferencing sessions, risking exposure of sensitive discussions, intellectual property, and personal data. Attackers could impersonate legitimate meetings or disrupt communications, impacting business continuity and trust. Organizations in sectors such as finance, healthcare, government, and education that rely heavily on Zoom integrated via WordPress are particularly vulnerable. The compromise of Zoom SDK keys could also facilitate further attacks on Zoom infrastructure or enable phishing campaigns using forged meeting invites. The breach of confidentiality and integrity could result in regulatory non-compliance under GDPR, leading to legal and financial penalties. Additionally, reputational damage from leaked or manipulated meetings could be severe. The ease of exploitation without authentication increases the likelihood of opportunistic attacks, especially in environments where patching is delayed.

CWE-287Improper Authentication (opens in a new tab)
Class weaknessLikelihood of exploit: HighOWASP Top 10 A07:2025: Authentication Failures (opens in a new tab)
When an actor claims to have a given identity, the product does not prove or insufficiently proves that the claim is correct.
MITRE discourages mapping vulnerabilities to this broad entry; the root cause is usually a more specific weakness.
Architecture and Design · Libraries or Frameworks
Use an authentication framework or library such as the OWASP ESAPI Authentication feature.
OWASP Cheat Sheets
OWASP Authentication (opens in a new tab)
OWASP ASVS 4.0.3
V2.8.5 (opens in a new tab)
V2.8.4 (opens in a new tab)
V9.2.3 (opens in a new tab)
Attack patterns
Fake the Source of Data (opens in a new tab)
Utilizing REST's Trust in the System Resource to Obtain Sensitive Data (opens in a new tab)
Session Hijacking (opens in a new tab)
Token Impersonation (opens in a new tab)
Upload a Web Shell to a Web Server (opens in a new tab)
From MITRE CWE, MITRE CAPEC and OWASP (Top 10, OpenCRE).

References

wpscan.com/vulnerability/218e6655-c5aa-4bce-86b2-cad3bb20020c/ (opens in a new tab)

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 18 Feb 2026, 06:29 UTC

Public exploits and detectiona Nuclei detection template

WeaknessesCWE-287

Technical details

References

Community reviews

Related threats