NAIMUR-EMAIL-OTP-FOR-WOOCOMMERCE · CVE-2026-104014 · Package
FIX → 2.1.1 ✓ verified
The Naimur Email OTP Verification for WooCommerce plugin, up to and including 2.1.0, lets an unauthenticated visitor finish a password reset for a victim's email once that victim has verified a reset code and not finished choosing a new password. The attacker gets a logged-in session cookie for that account, which is full site control if the account is an administrator.
first public Nov 7, 2026 · 2 sources
Check it with your coding agent
It checks your repository and tells you if you’re affected, with the fix.
Sites running the Naimur Email OTP Verification for WooCommerce plugin version 2.1.0 or earlier, which adds email OTP to WooCommerce password resets. Exposure depends on that plugin being active; sites without it are not affected. The sources do not say whether any configuration avoids the flaw.
Not affected if plugin-2.1.1-or-newer, plugin-newer-than-2.1.0, plugin-not-installed
Who cares account-takeover, auth-bypass, woocommerce, wordpress, wp-plugin
2.1.0 or lower is affectedUpgrade to 2.1.1
The Naimur Email OTP Verification for WooCommerce plugin for WordPress is vulnerable to authentication bypass in versions up to, and including, 2.1.0. This is due to the plugin's password-reset finalization endpoint (the wp_ajax_nopriv_ceovw_update_new_password action handled by CEOVW_AJAX::update_new_password()) authorizing the reset solely by the presence of a database row marking an email as 'VERIFIED', with no timestamp check, no session binding, and no per-reset token — combined with mark_otp_as_verified_for_reset() leaving the row in that state after a user enters their code (abandoning the flow leaves the row behind), and a scheduled 'ceovw_cleanup_expired_otps_event' cron that has no add_action() handler anywhere in the plugin so cleanup never runs. This makes it possible for unauthenticated attackers to take over any account whose owner previously requested and verified a password-reset code and did not immediately finish choosing a new password — the attacker needs only the victim's email address and a nonce that the plugin itself localizes publicly into the CEOVW_APP global on the WooCommerce account page for logged-out visitors, after which they call the endpoint, overwrite the victim's password, and are returned a live wordpress_logged_in_ session cookie for that user (full site takeover if the account is an administrator).
Are you affected?
Tell InfraStack what you run. It checks this one, and every next one, against your stack.
Ask from here. InfraStack checks the affected versions against your stack and answers in your inbox.
InfraStack checks the affected versions against your stack and answers in Slack, with the evidence and the fix.
Update the plugin to 2.1.1 or later (current wordpress.org release is 2.1.2). 2.1.1 was tagged 2026-11-02 as security fix for password reset.
NVD data is provided by NIST and is public domain. Posts quoted belong to their authors.