Skip to content
Laskyr

Plugins · customer-email-verification-for-woocommerce · data as of 2026-11-04

Is Customer Email Verification for WooCommerce safe? Known vulnerabilities and latest version

No known unpatched vulnerabilities in the latest version (2.8.4)

As of 2026-11-04. 1 issue is on record for older versions; version 2.8.3 or newer fixes all of them that state a fix.

Latest version
2.8.4
Last updated
2026-10-29
Active installs
2,000+
Known issues on record
1
Unpatched in latest
0
Tested up to WP
7.1.4 · PHP 7.2+

Block fake WooCommerce registrations with OTP email verification. Customers verify their email before their account is created — no code required. — by Zorem

What to do

  1. Update to the latest version (2.8.4). Anything older than 2.8.3 has at least one known issue listed below. Dashboard → Updates, or Plugins → “update now”.
  2. If you cannot update right away, deactivate it until you can.
  3. Turn on auto-updates for it: Plugins → “Enable auto-updates” on its row.
  4. If you ran a vulnerable version and something looks off (spam pages, strange admins, redirects), run the free scan.

With WP-CLI: wp plugin get customer-email-verification-for-woocommerce --field=version shows what you run; wp plugin update customer-email-verification-for-woocommerce updates it.

Check your version

Known vulnerabilities

1 on record, newest first. “Affected” is the version range the source gives; “fixed in” is the version the source names, or (marked *) the first wordpress.org release after the last affected version.

medium 4.8 CVE-2026-109236 · published 2026-10-28

Authentication bypass in Customer Email Verification for WooCommerce (2.8.2 and older)

Affected
2.8.2 and older
Fixed in
2.8.3 *
Access needed (per CVSS)
No login needed
Range from
CVE record (the advisory publisher) · score by Wordfence
Details from the advisory

The Customer Email Verification for WooCommerce plugin for WordPress is vulnerable to Authentication Bypass via a Predictable Email-Verification Token in all versions up to, and including, 2.8.2. This is due to the `authenticate_user_by_email_link()` function — hooked on the `wp` action and triggered by the `cusomer_email_verify` GET parameter — lacking any capability check or nonce verification, while the `secret_code` it validates is generated as `md5(email . time())` and the `verify_otp_nonce` required to trigger token issuance via the `wp_ajax_nopriv_resend_otp` handler is emitted to every front-end visitor through `wp_localize_script`. This makes it possible for unauthenticated attackers to log in as a newly created, verified WooCommerce customer bound to an arbitrary email address — or to flip an existing account's `customer_email_verified` meta to verified — fully bypassing the plugin's core email-verification control. Exploitation requires the `cev_user_log` table to contain a `password` column, which is absent from the fresh-install schema shipped in version 2.8.2 but is present on sites upgraded from an older version where that column was defined.

NVD CVE-2026-109236Wordfence advisorywordpress.orgPlugin source

Recent activity

Browse vulnerabilities

Where this data comes from

Badge for your site or docs (states facts with a date, not a verdict):
Customer Email Verification for WooCommerce vulnerability status badge
<a href="https://laskyr.com/plugins/customer-email-verification-for-woocommerce"><img src="https://laskyr.com/plugins/customer-email-verification-for-woocommerce/badge.svg" alt="Customer Email Verification for WooCommerce vulnerability status"></a>

← Check another plugin · Free hacked-site scan

First hour checklist

If the site was just hacked, read the emergency kit before you delete files. The page is free. Email is optional.

Read the emergency kit