Read the docs

Authentication bypass in Naimur Email OTP for WooCommerce

Priority MEDIUM 46CWE-287Published · Updated

Key facts

Attack vector
Network
Privileges required
None
User interaction
None
Attack complexity
Low
Impact type
Security bypass
Confidentiality · integrity · availability
High · High · High
Fix status
No fix listed

Attack profile from CVSS 3.1 · CNA. Fix status from CNA. Impact type from CWE-287.

Summary

The Naimur Email OTP Verification for WooCommerce WordPress plugin up to and including 2.1.0 fails to properly authenticate password resets (CWE-287). A password reset row marked as verified stays in place after a user abandons the flow, and it is never cleaned up. An unauthenticated attacker who has a victim's email address and the public nonce can overwrite the victim's password and receive a logged in session cookie for that account, including administrator accounts.

Written with Claude Haiku 5.5 from the sources below · 2026-11-07

Description from the CNA

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).

Why it matters now

Exploitation None reported CISA SSVC · not in CISA KEV
Fix No fix listed No fixed version in the sources yet

SSVC decision points

CISA ADP · SSVC 2.0.3

Exploitation
None
Automatable
Yes
Technical impact
Total

The decision (Track, Attend, Act) also depends on your mission and well-being impact; see CISA's SSVC guide.

Affected products

VendorProductAffected versionsFixed inStatusSource
naimurrahmannahidNaimur Email OTP Verification for WooCommerceup to 2.1.0—No fix listedCNA
  • Naimur Email OTP Verification for WooCommerce Vendornaimurrahmannahid Affected up to 2.1.0 Fixed in — No fix listed CNA

Remediation

The sources list no fixed version for Naimur Email OTP Verification for WooCommerce.

Written with Claude Haiku 5.5 from the sources below · 2026-11-07

Timeline

  1. 2026-11-07 Threatist record created from CVE-2026-104014
  2. 2026-11-07 Alias added: GHSA-92r9-422h-xw35
  3. 2026-11-07 CISA SSVC decision points changed

References

Sources