CVE-2026-2374
HighSummary
The Login No Captcha reCAPTCHA plugin for WordPress is vulnerable to Stored Cross-Site Scripting (XSS) in versions up to 1.8.0. The issue arises from the `authenticate()` function storing unsanitized data in the `login_nocaptcha_error` option during login attempts from a non-standard login page.
Risk Assessment
Attackers can inject arbitrary web scripts that execute when an administrator with a whitelisted IP address visits the WordPress dashboard. This poses a serious threat to data security and system integrity.
Recommendation
It is recommended to update the plugin to the latest version to mitigate this vulnerability. Additionally, conducting a security audit is advisable to minimize the risk associated with XSS attacks.
Original NVD description (English source)
The Login No Captcha reCAPTCHA plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the `$_SERVER['PHP_SELF']` superglobal in all versions up to, and including, 1.8.0. This is due to the `authenticate()` function storing the unsanitized output of `basename($_SERVER['PHP_SELF'])` in the `login_nocaptcha_error` WordPress option when a login attempt is made from a non-standard login page (e.g., xmlrpc.php). The `admin_notices()` function then echoes this stored value directly into the admin dashboard HTML without escaping. This makes it possible for unauthenticated attackers to inject arbitrary web scripts that execute when an administrator with a whitelisted IP address visits the WordPress dashboard within 30 seconds of the attack.