Skip to main content
Vulnerability Database/CVE-2026-104745

CVE-2026-104745: WooCommerce Email Verification Privilege Escalation

CVE-2026-104745 is a privilege escalation vulnerability in the Customer Email Verification for WooCommerce plugin that allows attackers to gain unauthorized access to any unverified account. This article covers technical details, affected versions, exploitation requirements, and mitigation strategies.

Published:

Disclaimer: This content was generated using AI. While we strive for accuracy, please verify critical information with official sources.

Sources: National Vulnerability Database, CISA KEV, Exploit-DB

CVE-2026-104745 Overview

CVE-2026-104745 is a privilege escalation vulnerability in the Customer Email Verification for WooCommerce plugin for WordPress, affecting versions up to and including 3.3.0. The flaw lives in the alg_wc_ev_generate_user_code() function, which generates per-user activation secrets using wp_rand(100) when the plugin's Encoding method is set to hashids. This produces roughly 101 possible values (approximately 7 bits of entropy), with no cryptographic message authentication code (MAC) protecting the token. An unauthenticated attacker can brute-force the activation code space and authenticate as any unverified WordPress account, including administrators. The weakness is categorized under [CWE-269: Improper Privilege Management].

Critical Impact

Unauthenticated attackers can authenticate as any unverified WordPress user, including administrators, by brute-forcing a trivially small activation code space through a forged verification URL.

Affected Products

  • Customer Email Verification for WooCommerce plugin for WordPress
  • All versions up to and including 3.3.0
  • Installations configured with the non-default hashids Encoding method

Discovery Timeline

  • 2026-10-16 - CVE-2026-104745 published to the National Vulnerability Database (NVD)
  • 2026-10-16 - Last updated in the NVD database

Technical Details for CVE-2026-104745

Vulnerability Analysis

The vulnerability stems from insufficient entropy in activation token generation combined with an unauthenticated handler that acts directly on attacker-controlled input. When the plugin's Encoding method is set to hashids, the alg_wc_ev_generate_user_code() function calls wp_rand(100) to produce the per-user activation secret. The result is encoded with Hashids, a reversible encoding scheme that provides obfuscation but no cryptographic integrity.

The verify() handler is hooked to the init action at PHP_INT_MAX, runs for unauthenticated requests, and accepts the ?alg_wc_ev_verify_email= GET parameter without a WordPress nonce check or rate limiting. An attacker who recovers the Hashids salt can enumerate the ~101 possible codes for any unverified account and complete verification as that user.

Root Cause

The root cause is weak randomness in wp_rand(100) paired with a reversible, unauthenticated encoding. Hashids is not a MAC, so the token cannot be validated for integrity. The default salt is derived from md5(time()) at first initialization, which an attacker can bound and brute-force. Together these choices violate [CWE-269] by granting authentication authority based on a guessable value.

Attack Vector

Exploitation is network-based and requires no authentication or user interaction. The attacker must identify a target WordPress site running the vulnerable plugin with the hashids Encoding method enabled. The attacker recovers or brute-forces the Hashids salt, then issues forged verification URLs containing enumerated alg_wc_ev_verify_email values against the target user. Because the handler lacks rate limiting, the small code space can be exhausted quickly, and a successful match authenticates the attacker as the targeted unverified account.

No verified public exploit code is available. See the Wordfence Vulnerability Report and the vulnerable WordPress Plugin Core Method for technical details.

Detection Methods for CVE-2026-104745

Indicators of Compromise

  • High-volume GET requests to site URLs containing the alg_wc_ev_verify_email parameter from a single source IP within a short window.
  • Successful WordPress authentication events for accounts that had never completed email verification.
  • New administrator sessions originating from IPs with no prior login history for the targeted account.
  • Plugin configuration changes setting the Encoding method to hashids.

Detection Strategies

  • Inspect web server access logs for repeated requests to /?alg_wc_ev_verify_email= with sequential or enumerated token values.
  • Correlate verification handler hits on the init action with subsequent session creation for the same user ID.
  • Audit the wp_options table for the plugin's Encoding method value and flag any site using hashids.

Monitoring Recommendations

  • Monitor WordPress authentication logs for first-time logins to accounts flagged as unverified.
  • Alert on bursts of requests to the plugin's verification endpoint exceeding a defined per-IP threshold.
  • Track administrative role assignments and privileged action telemetry for anomalies following verification events.

How to Mitigate CVE-2026-104745

Immediate Actions Required

  • Update the Customer Email Verification for WooCommerce plugin to a version newer than 3.3.0 as soon as the vendor publishes a fixed release.
  • Change the plugin's Encoding method away from hashids to the default encoding until a patched version is deployed.
  • Audit all WordPress accounts for unverified status and remove or verify stale administrator accounts.
  • Rotate credentials and invalidate active sessions for any administrator account that may have been targeted.

Patch Information

Review the vendor WordPress Plugin Changeset and the Wordfence Vulnerability Report for remediation status. Upgrade to a plugin release that replaces wp_rand(100) with a cryptographically secure random source and adds a MAC-protected token with rate limiting on the verification handler.

Workarounds

  • Revert the Encoding method setting to the default (non-hashids) option in the plugin configuration.
  • Deploy a web application firewall (WAF) rule to rate-limit requests containing the alg_wc_ev_verify_email parameter.
  • Restrict access to the WordPress site's verification endpoint by IP allowlist where feasible.
  • Force email verification completion for all existing accounts to remove the unverified attack surface.
bash
# Example WAF rule concept (ModSecurity-style) to rate-limit verification attempts
SecRule REQUEST_URI "@contains alg_wc_ev_verify_email" \
    "id:1026104745,phase:1,deny,status:429,\
     msg:'CVE-2026-104745 verification brute-force attempt',\
     setvar:ip.verify_count=+1,expirevar:ip.verify_count=60"
SecRule IP:verify_count "@gt 5" \
    "id:1026104746,phase:1,deny,status:429,\
     msg:'Rate limit exceeded on email verification endpoint'"

Disclaimer: This content was generated using AI. While we strive for accuracy, please verify critical information with official sources.

Sources: National Vulnerability Database, CISA KEV, Exploit-DB

Experience the Most Advanced Cybersecurity Platform

See how the world’s most intelligent, autonomous cybersecurity platform can protect your organization today and into the future.