CVE-2026-104745 wpcodefactory CVE debrief

Who should care

Defenders responsible for WordPress deployments using the Customer Email Verification for WooCommerce plugin, especially those with administrator-level accounts, should assess exposure and prioritize verification of the plugin version and configuration.

Why it matters

CVE-2026-104745 is a Privilege Escalation vulnerability in the Customer Email Verification for WooCommerce plugin for WordPress. Defenders should prioritize verifying the plugin version, assessing exposure, and taking steps to secure the deployment, as exploitation could lead to authentication as unverified accounts.

• Potential authentication as unverified WordPress accounts, including administrator-level accounts
• Possible exploitation via forged verification URLs
• Need for verification of plugin version and configuration
• Priority for changing 'Encoding method' setting and recovering or resetting Hashids salt

Technical summary

The Customer Email Verification for WooCommerce plugin for WordPress is vulnerable to Privilege Escalation. The `alg_wc_ev_generate_user_code()` function generates per-user activation secrets using `wp_rand(100)` when the 'Encoding method' is set to 'hashids', producing only ~101 possible values. The unauthenticated `verify()` handler accepts and acts on the attacker-controlled `?alg_wc_ev_verify_email=` GET parameter directly, allowing for brute-force attacks on the activation code space.

Defensive priority

Defenders should prioritize verifying the plugin version and assessing exposure, as exploitation requires changing the 'Encoding method' setting to 'hashids' and recovering or brute-forcing the Hashids salt.

Recommended defensive actions

• Verify the plugin version and assess exposure
• Change the 'Encoding method' setting to a secure value if currently set to 'hashids'
• Recover or reset the Hashids salt if necessary
• Monitor for suspicious verification URLs and authentication attempts
• Review compensating controls for exposed systems while remediation is scheduled and verified
• Check relevant monitoring, detection, and logs for exposed assets that need extra review
• Track exceptions, retest remediated assets, and close the item only after evidence is documented

Evidence notes

The vulnerability details are based on the CVE record and source references provided. However, the corpus does not establish versions beyond 3.3.0, exploitation, impact, or remediation for all affected deployments, suggesting a need for verification from official sources.

Sources and references

Methodology and review provenance

AI-assisted synthesis based on stored public vulnerability evidence. System validation, approval state, and publication status do not by themselves establish human review of this revision. PatchSiren helps prioritize defensive review and does not prove exposure or remediation on any system.