Skip to main content

WPZOOM Connect EUVDEUVD-2026-91911

| CVE-2026-100149 MEDIUM
Information Exposure (CWE-200)
2026-10-03 Wordfence GHSA-rhmj-6pg3-6h84
5.3
CVSS 3.1 · Vendor: Wordfence
View

Attack ChainAIDerived

Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain

  1. Access
    Identify WooCommerce/EDD store running WPZOOM Connect
  2. Delivery
    Register subscriber account with crafted email
  3. Exploit
    Harvest x-yamidoo-signature from page HTML
  4. Execution
    Replay signature to pass verify_request for victim
  5. Impact
    Exfiltrate arbitrary victim PII and license keys

Vulnerability Assessment

Weakness
CWE
OWASP Top 10:2025
A01:2025 - Broken Access Control
ASVS 5.0
V14 - Data Protection Data exposure prevention
MITRE ATT&CK

2 techniques across 2 tactics: Collection, Discovery

The technique list with ATT&CK links and the kill-chain view is part of the Basic plan and up.

Exploitation Conditions

Requires: (1) WPZOOM Connect ≤4.7.3 active with a live Yamidoo AI chat connection; (2) WooCommerce and/or Easy Digital Downloads (with EDD Software Licensing for license-key exposure) present with real customer data; (3) the share_customer_data and identify_logged_in settings enabled - both are ON by default, so NO non-default configuration is needed; and (4) the ability to register a WooCommerce customer or subscriber-level account whose email local part encodes the target timestamp and victim email so the inline_js()-printed signature passes verify_request(). Limiting factors: the attacker must be able to create an account (open registration), must correctly craft the encoding email, and the disclosed data is bounded to the chat customer-card fields (though for any arbitrary victim email on the site).

Impact

Signals are mixed and point to a genuine but mid-tier priority. The CVSS base score is 5.3 (Medium) with vector AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N - network-reachable, low-complexity, and nominally unauthenticated with only a limited confidentiality impact and no integrity/availability effect. No EPSS probability, no CISA KEV listing, and no public exploit code were supplied, so there is no public exploit identified at time of analysis and no evidence of active exploitation. However, two input signals conflict with the raw score and should temper reliance on it. First, the CVSS vector claims PR:N (unauthenticated), but the description explicitly requires the attacker to register a WooCommerce customer or subscriber-level account with a crafted email - in practice this is a low-privilege (PR:L) precondition, trivially met only where self-registration is open. Second, C:L understates the actual exposure: the flaw yields the full customer card - name, WordPress user ID, order history/totals, purchased products, payment-method labels, and EDD Software Licensing keys with activation counts - for ANY arbitrary victim email on the site, which is a serious confidentiality impact for e-commerce/licensing stores. Because the vulnerable features (share_customer_data and identify_logged_in) are enabled by default, affected sites are exposed without any special configuration. Net: a real, broadly-reachable PII and license-key disclosure that merits prompt patching for WooCommerce/EDD stores, but without current exploitation evidence it is not an emergency on the level of a KEV-listed RCE.

Exploit ScenarioDerived

An attacker self-registers a WooCommerce customer or subscriber account on a store running WPZOOM Connect ≤4.7.3, using an email whose local part encodes a chosen timestamp and the victim's email address. They load a front-end page where inline_js() prints an x-yamidoo-signature into the HTML, harvest that signature, and replay it against verify_request() so it validates for the victim rather than themselves - returning the victim's complete customer card including PII, order history, and EDD license keys. No public exploit code has been identified, but the technique is deterministic and requires no special timing.

This Month Plan within 30 days. Why: MEDIUM severity (CVSS 4.0-6.9).
No patch listed yet 0.3% exploitation probability (EPSS)

Get an e-mail when this CVE is exploited, patched or re-scored. Free account.

Alert me

AnalysisAIv1 – Oct 03, 2026

Sensitive customer data disclosure in WPZOOM Connect through 4.7.3 allows an authenticated low-privilege WooCommerce customer/subscriber to retrieve full customer card data for any arbitrary victim email, including names, WordPress user IDs, order histories, totals, purchased products, payment method labels, and EDD Software Licensing license keys with status and activation counts. The issue is caused by the 'x-yamidoo-signature' printed by inline_js() being forgeable: an attacker registers a crafted email whose local part encodes the target timestamp and victim email, making verify_request() accept the signature; share_customer_data and identify_logged_in are enabled by default, so no non-default configuration is required. The assessed vector is CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N, indicating high confidentiality impact but no integrity/availability impact, and no public exploit code or CISA KEV active exploitation was identified at time of analysis.

RemediationAI

Upstream fix available (PR/commit); released patched version not independently confirmed. Apply the WPZOOM fix or upgrade beyond 4.7.3 when a vendor advisory specifies the exact patched version; references include the Wordfence advisory at https://www.wordfence.com/threat-intel/vulnerabilities/id/e0c9026c-d83e-41ac-be3a-93a33c32c47b?source=cve, tag 4.7.3 source at https://plugins.trac.wordpress.org/browser/social-icons-widget-by-wpzoom/tags/4.7.3/includes/classes/class-wpzoom-ai-chat-customer.php#L82, and GitHub commit https://github.com/wpzoom/social-icons-widget-by-wpzoom/commit/351a873ac6c99fd8fb63115628a9d612427c3097. Immediate compensating controls: disable the share_customer_data and identify_logged_in settings in WPZOOM Connect/Yamidoo to stop the customer card from being generated for chat requests, accepting loss of AI chat customer lookup/personalization; if the chat integration is not required, deactivate WPZOOM Connect until a patched release is confirmed. Because the attack requires creating a low-privilege WooCommerce customer/subscriber account, close open registration or require approval if operationally possible, but this may disrupt e-commerce onboarding. If EDD Software Licensing is in use, consider removing license-key display from the customer card or restricting that section, accepting reduced customer self-service for license management. Monitor for unusual registrations with email local parts that encode timestamps/victim addresses and review x-yamidoo-signature access patterns.

Affected VersionsENISA

WPZOOM Connect: AI Chat, Click to Chat, Social Icons & Share Buttons 0 ≤4.7.3

Affected Packages

euvd wpzoom_connect_ai_chat_click_to_chat_social_icons_share_buttons no fix

Source: OSV (Open Source Vulnerabilities)

Affects your stack

Affects 1 package in euvd

Checking this CVE against your own stacks and servers is part of the Basic plan and up.

Technical ContextAI · show details

CWE-200 information exposure. CPE cpe:2.3:a:wpzoom:wpzoom_connect:_ai_chat,_click_to_chat,_social_icons_&_share_buttons:*:*:*:*:*:*:*:* identifies the WPZOOM Connect plugin. The vulnerable flow lives in the Yamidoo AI chat integration: inline_js() prints a signature into page HTML, and verify_request() trusts it. Because the signature is not tied to an authenticated server-side session or the victim's identity, a low-privileged account with a crafted email local part can satisfy verification. The default-enabled share_customer_data and identify_logged_in settings then cause the chat customer card to expose WooCommerce order/subscription data and EDD Software Licensing license keys. References point to tag 4.7.3 code in class-wpzoom-ai-chat-customer.php around lines 82 and 93 and class-wpzoom-ai-chat.php around line 921.

Know when Wpzoom Connect gets its next vulnerability

  • Watch products and get an email when something new is published
  • Check this CVE against your own stack and servers
  • Exploit and PoC references, threat intelligence from 22 sources

No credit card · 7-day full trial

Severity by source

Vendor (Wordfence) PRIMARY 5.3 MEDIUM
AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N
vuln.today AI 6.5 MEDIUM

Attacker must register and use an account to harvest the replayable signature (PR:L); crafting is deterministic (AC:L); disclosure of arbitrary victims' PII and EDD license keys is a serious confidentiality loss (C:H), with no integrity/availability impact.

3.1 AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N
4.0 AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:N/VA:N/SC:N/SI:N/SA:N

Primary rating from Vendor (Wordfence).

CVSS VectorVendor: Wordfence

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

DescriptionCVE.org

The WPZOOM Connect: AI Chat, Click to Chat, Social Icons & Share Buttons plugin for WordPress is vulnerable to Sensitive Information Exposure in all versions up to, and including, 4.7.3 via the 'x-yamidoo-signature (attacker-obtained via inline_js identify payload)' parameter. This makes it possible for unauthenticated attackers to extract the full customer card - including name, WordPress user ID, order history, order totals, purchased products, payment method labels, and EDD Software Licensing license keys with status and activation counts - for any arbitrary victim email address on the site. Exploitation requires the attacker to register a WooCommerce customer or subscriber-level account with a crafted email address whose local part encodes the target timestamp and victim email, allowing the signature printed into the page HTML by inline_js() to pass verify_request() for an arbitrary victim; both the share_customer_data and identify_logged_in settings are enabled by default, so no non-default configuration is required.

Threat Intelligence Overview

EPSS Score
0.3%
Top 77% exploitable
Prevalence
Medium
popular WPZOOM WordPress plugin, moderate install base
Data Quality
6 sources
Confidence: High

How this decision was reached

The engine reads each signal below and applies a fixed list of rules from top to bottom. The first rule that matches sets the recommended action – like a statement, every line is shown.

SignalValue
Severity MEDIUM
CISA KEV No
Public POC No
EPSS 0.3%
Patch available No
Active threat No
Deciding rule
MEDIUM severity (CVSS 4.0-6.9)
What every action level means
Emergency Immediate action required. Criteria: CRITICAL + in CISA KEV (actively exploited) without patch, OR CRITICAL + EPSS > 30% without patch, OR CRITICAL + active threat signals without patch.
Act Now Prioritize within 24-48h. Criteria: in KEV with patch available, OR CRITICAL + public POC, OR HIGH + EPSS > 10%, OR CRITICAL + active threat, OR any CRITICAL severity.
This Week Schedule remediation this week. Criteria: HIGH severity (CVSS 7.0-8.9). Patch within normal change window.
This Month Plan within 30 days. Criteria: MEDIUM severity (CVSS 4.0-6.9), lower exploitation probability. Include in regular patch cycle.
Monitor Track and reassess. Criteria: LOW severity (CVSS 0.1-3.9), minimal exploitation risk. No immediate action needed.

SSVC AssessmentENISA

SSVC Decision· derived
Scheduled
Exploitation
None
System Exposure· derived
Open
Automatable
Yes
Human Impact· derived
Medium
Technical Impact
Partial

Priority Score

26
Low Medium High Critical
KEV: 0
EPSS: 0
CVSS: +26
PoC: 0
Weaponized: 0
Threat intel: 0
Gov advisory: 0

Attack Technique

Information disclosure occurs when an application unintentionally exposes sensitive data that aids attackers in reconnaissance or directly compromises security.

This site uses cookies essential for authentication and security. No tracking or analytics cookies are used. Privacy Policy