CVE-2025-12374: CWE-287 Improper Authentication in pickplugins User Verification by PickPlugins
The Email Verification, Email OTP, Block Spam Email, Passwordless login, Hide Login, Magic Login – User Verification plugin for WordPress is vulnerable to authentication bypass in all versions up to, and including, 2.0.39. This is due to the plugin not properly validating that an OTP was generated before comparing it to user input in the "user_verification_form_wrap_process_otpLogin" function. This makes it possible for unauthenticated attackers to log in as any user with a verified email address, such as an administrator, by submitting an empty OTP value.
AI Analysis
Technical Summary
CVE-2025-12374 is a critical vulnerability classified under CWE-287 (Improper Authentication) found in the 'User Verification by PickPlugins' WordPress plugin, which provides features like Email Verification, Email OTP, Passwordless login, and Magic Login. The vulnerability exists in all versions up to and including 2.0.39 due to improper validation logic in the 'user_verification_form_wrap_process_otpLogin' function. Specifically, the plugin does not verify whether an OTP was actually generated before comparing the user-submitted OTP value. This logical flaw allows an attacker to bypass the OTP verification step by submitting an empty OTP, effectively bypassing authentication controls. Consequently, an unauthenticated attacker can log in as any user with a verified email address, including high-privilege accounts such as administrators. The vulnerability has a CVSS v3.1 base score of 9.8, reflecting its critical nature with network attack vector, no required privileges, no user interaction, and full impact on confidentiality, integrity, and availability. Although no public exploits have been observed, the ease of exploitation and the severity of impact make this a high-risk threat. The lack of available patches necessitates immediate defensive actions to prevent exploitation. The vulnerability affects a widely used WordPress plugin, increasing the potential attack surface for websites relying on it for user verification and authentication.
Potential Impact
For European organizations, this vulnerability poses a severe risk of unauthorized access to WordPress websites and associated backend systems. Attackers exploiting this flaw can impersonate any user, including administrators, leading to full site compromise. This can result in data breaches involving sensitive customer and employee information, defacement of websites, insertion of malicious content, or use of compromised sites as pivot points for further network intrusion. The integrity and availability of web services can be severely disrupted, affecting business operations and reputation. Given the widespread use of WordPress across Europe, especially in sectors like e-commerce, government, education, and media, the potential impact is extensive. Organizations with compliance obligations under GDPR face additional risks of regulatory penalties due to unauthorized data access. The vulnerability's ease of exploitation without authentication or user interaction further elevates the threat level, making it a prime target for automated attacks and mass exploitation campaigns.
Mitigation Recommendations
Until an official patch is released, European organizations should take immediate and specific actions to mitigate this vulnerability: 1) Disable or uninstall the 'User Verification by PickPlugins' plugin to eliminate the attack vector. 2) If disabling the plugin is not feasible, restrict access to the WordPress login page using IP whitelisting or VPN-only access to limit exposure. 3) Implement Web Application Firewall (WAF) rules to detect and block login attempts with empty OTP values or anomalous authentication patterns related to this plugin. 4) Enforce multi-factor authentication (MFA) at the WordPress level or via external identity providers to add an additional security layer. 5) Monitor WordPress logs for suspicious login attempts or unusual user activity, focusing on accounts with verified emails. 6) Prepare for rapid patch deployment by subscribing to vendor notifications and security mailing lists. 7) Conduct an audit of all WordPress sites within the organization to identify installations of the vulnerable plugin and prioritize remediation. 8) Educate administrators about the risk and ensure strong password policies are in place as a secondary defense.
Affected Countries
Germany, France, United Kingdom, Italy, Netherlands, Spain, Poland, Sweden
CVE-2025-12374: CWE-287 Improper Authentication in pickplugins User Verification by PickPlugins
Description
The Email Verification, Email OTP, Block Spam Email, Passwordless login, Hide Login, Magic Login – User Verification plugin for WordPress is vulnerable to authentication bypass in all versions up to, and including, 2.0.39. This is due to the plugin not properly validating that an OTP was generated before comparing it to user input in the "user_verification_form_wrap_process_otpLogin" function. This makes it possible for unauthenticated attackers to log in as any user with a verified email address, such as an administrator, by submitting an empty OTP value.
AI-Powered Analysis
Technical Analysis
CVE-2025-12374 is a critical vulnerability classified under CWE-287 (Improper Authentication) found in the 'User Verification by PickPlugins' WordPress plugin, which provides features like Email Verification, Email OTP, Passwordless login, and Magic Login. The vulnerability exists in all versions up to and including 2.0.39 due to improper validation logic in the 'user_verification_form_wrap_process_otpLogin' function. Specifically, the plugin does not verify whether an OTP was actually generated before comparing the user-submitted OTP value. This logical flaw allows an attacker to bypass the OTP verification step by submitting an empty OTP, effectively bypassing authentication controls. Consequently, an unauthenticated attacker can log in as any user with a verified email address, including high-privilege accounts such as administrators. The vulnerability has a CVSS v3.1 base score of 9.8, reflecting its critical nature with network attack vector, no required privileges, no user interaction, and full impact on confidentiality, integrity, and availability. Although no public exploits have been observed, the ease of exploitation and the severity of impact make this a high-risk threat. The lack of available patches necessitates immediate defensive actions to prevent exploitation. The vulnerability affects a widely used WordPress plugin, increasing the potential attack surface for websites relying on it for user verification and authentication.
Potential Impact
For European organizations, this vulnerability poses a severe risk of unauthorized access to WordPress websites and associated backend systems. Attackers exploiting this flaw can impersonate any user, including administrators, leading to full site compromise. This can result in data breaches involving sensitive customer and employee information, defacement of websites, insertion of malicious content, or use of compromised sites as pivot points for further network intrusion. The integrity and availability of web services can be severely disrupted, affecting business operations and reputation. Given the widespread use of WordPress across Europe, especially in sectors like e-commerce, government, education, and media, the potential impact is extensive. Organizations with compliance obligations under GDPR face additional risks of regulatory penalties due to unauthorized data access. The vulnerability's ease of exploitation without authentication or user interaction further elevates the threat level, making it a prime target for automated attacks and mass exploitation campaigns.
Mitigation Recommendations
Until an official patch is released, European organizations should take immediate and specific actions to mitigate this vulnerability: 1) Disable or uninstall the 'User Verification by PickPlugins' plugin to eliminate the attack vector. 2) If disabling the plugin is not feasible, restrict access to the WordPress login page using IP whitelisting or VPN-only access to limit exposure. 3) Implement Web Application Firewall (WAF) rules to detect and block login attempts with empty OTP values or anomalous authentication patterns related to this plugin. 4) Enforce multi-factor authentication (MFA) at the WordPress level or via external identity providers to add an additional security layer. 5) Monitor WordPress logs for suspicious login attempts or unusual user activity, focusing on accounts with verified emails. 6) Prepare for rapid patch deployment by subscribing to vendor notifications and security mailing lists. 7) Conduct an audit of all WordPress sites within the organization to identify installations of the vulnerable plugin and prioritize remediation. 8) Educate administrators about the risk and ensure strong password policies are in place as a secondary defense.
Affected Countries
Technical Details
- Data Version
- 5.2
- Assigner Short Name
- Wordfence
- Date Reserved
- 2025-10-27T21:22:35.296Z
- Cvss Version
- 3.1
- State
- PUBLISHED
Threat ID: 69327c01f88dbe026c7c159b
Added to database: 12/5/2025, 6:30:25 AM
Last enriched: 12/12/2025, 7:16:14 AM
Last updated: 1/19/2026, 8:41:59 PM
Views: 123
Community Reviews
0 reviewsCrowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.
Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.
Related Threats
CVE-2026-23852: CWE-94: Improper Control of Generation of Code ('Code Injection') in siyuan-note siyuan
MediumCVE-2026-1174: Resource Consumption in birkir prime
MediumCVE-2026-23837: CWE-863: Incorrect Authorization in franklioxygen MyTube
CriticalCVE-2026-23851: CWE-22: Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal') in siyuan-note siyuan
HighCVE-2026-23850: CWE-22: Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal') in siyuan-note siyuan
HighActions
Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.
Need more coverage?
Upgrade to Pro Console in Console -> Billing for AI refresh and higher limits.
For incident response and remediation, OffSeq services can help resolve threats faster.