---
id: "CVE-2026-104745"
kind: "vulnerability"
aliases: ["CVE-2026-104745"]
title: "WordPress WooCommerce email verification plugin: unauthenticated admin account takeover"
severity: "high"
cvss: 8.1
epss: null
exploited: false
status: "open"
category: "package"
products: []
ecosystems: []
tags: ["package", "self-hosted", "woocommerce", "wordpress"]
not_affected_if: ["default-config", "plugin-not-installed"]
published_at: "2026-10-16T04:18:21+00:00"
first_seen_at: "2026-10-23T21:57:12+00:00"
updated_at: "2026-10-25T03:07:55+00:00"
sources: [{"source": "nvd", "url": "https://nvd.nist.gov/vuln/detail/CVE-2026-104745", "first_seen_at": "2026-10-23T21:57:12+00:00"}]
---

# WordPress WooCommerce email verification plugin: unauthenticated admin account takeover

The 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, check and fix written by a model from the sources; labelled as such._

## How to check

- Check the installed plugin version in the WordPress admin plugin list or in `wp-content/plugins/` for the Customer Email Verification for WooCommerce plugin; versions `3.3.0` and below are affected.
- In the plugin settings, check whether 'Encoding method' is set to 'hashids' (non-default).

## Fix

- Update the Customer Email Verification for WooCommerce plugin to a version later than `3.3.0` (fixed version unknown from the sources).
- Until patched, switch 'Encoding method' away from 'hashids' or deactivate the plugin.

## Timeline

- 2026-10-23T21:57:12+00:00 nvd https://nvd.nist.gov/vuln/detail/CVE-2026-104745

## From the sources

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.

---

_Free to read at a human pace. An API with keys and an MCP server are in preparation; early access: hello@infrastack.ai_