# CVE-2026-104745: Privilege escalation in Customer Email Verification for WooCommerce

> Unauthenticated attackers can escalate privileges to administrator by brute-forcing weak activation codes in a specific non-default configuration of the WooCommerce email verification plugin.

- **Severity:** High 8.1 (`CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 16 Oct 2026
- **Updated:** 16 Oct 2026
- **Also known as:** GHSA-hrmj-f3f9-pq8r

## What is CVE-2026-104745?

CVE-2026-104745 is a high-severity vulnerability in wpcodefactory Customer Email Verification for WooCommerce, published on 16 Oct 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

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.

Weakness: CWE-269 (Improper Privilege Management)

## Which versions are affected by CVE-2026-104745?


## How do I fix CVE-2026-104745?

No fix has been published for CVE-2026-104745 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-104745 being exploited?

There is no known exploitation of CVE-2026-104745 in the wild and no public exploit code.

Public exploit code:

- CVE-2026-104745 is a high-severity vulnerability rated 8.1/10 on the CVSS scale. 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. (github_poc): https://github.com/rxsklife/CVE-2026-104745

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-104745 and fix it if it is affected.

What it is: CVE-2026-104745 is a high-severity vulnerability in wpcodefactory Customer Email Verification for WooCommerce, published on 16 Oct 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-104745 in the wild and no public exploit code.

Affected product: wpcodefactory Customer Email Verification for WooCommerce. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-104745/ (Markdown: https://insights.sbomify.com/CVE-2026-104745/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-104745
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-104745
- OSV: https://osv.dev/vulnerability/CVE-2026-104745

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-104745/
Summaries are generated and may contain mistakes; the official description above is the record.