Live › vulnerability › CVE-2026-104745
Go to dashboardThe Customer Email Verification for WooCommerce plugin (up to and including 3.3.0) generates its activation code from only about 101 possible values when the Hashids encoding method is selected. An unauthenticated attacker can brute-force that code through a crafted verification URL and log in as any unverified WordPress account, including administrators.
Summary written from the sources below. Check the originals before acting.
First seen by InfraStack 2026-10-23 21:57 UTC. All times on this page are UTC.
Sites running the Customer Email Verification for WooCommerce plugin at version 3.3.0 or earlier with the non-default 'hashids' encoding method enabled. Exposure also requires that target accounts, especially administrator accounts, still have an unverified email address. Sites without this plugin, or running it with the default encoding method, are not affected by this description.
No product ranges from the sources yet.
wp-content/plugins/ for the Customer Email Verification for WooCommerce plugin; versions 3.3.0 and below are affected.3.3.0 (fixed version unknown from the sources).Each row is the first time that source carried this signal. The analyst’s rows are its own findings.
The Customer Email Verification for WooCommerce plugin for WordPress is vulnerable to Privilege Escalation via the alg_wc_ev_verify_email parameter in versions up to, and including, 3.3.0. The vulnerability exists because alg_wc_ev_generate_user_code() generates the per-user activation secret using wp_rand(100) when the plugin's 'Encoding method' is set to 'hashids', producing only ~101 possible values (~7 bits of entropy); the resulting token is a reversible Hashids encoding with no cryptographic MAC, and the unauthenticated verify() handler — hooked to init at PHP_INT_MAX with no nonce check and no rate limiting — accepts and acts on the attacker-controlled ?alg_wc_ev_verify_email= GET parameter directly. This makes it possible for unauthenticated attackers to gain authentication as any unverified WordPress account, including administrator-level accounts, by brute-forcing the trivially small activation code space via a forged verification URL. Exploitation requires that the 'Encoding method' setting be changed to 'hashids' (non-default), that the attacker recover or brute-force the Hashids salt (which defaults to an md5(time()) value set at first initialization), and that the target account's email address remain unverified.
This page as .md · .json · in your agent: get_signal("CVE-2026-104745")
NVD data is provided by NIST and is public domain. Posts quoted belong to their authors.