HomeWordPress vulnerabilitiesLogin No Captcha reCAPTCHA
Login No Captcha reCAPTCHA vulnerabilities
Login No Captcha reCAPTCHA has 2 known vulnerabilities in this database. The most recent published record is dated 28 May 2026.
- Known vulnerabilities
- 2
- Active installs
- 50,000+
- Latest version
- 1.8.1
- Last updated
- 26 May 2026
- Most recent
- 28 May 2026
Find it in your WordPress dashboard under Plugins. Severity is based on the CVSS score published with the CVE where one is available.
| Vulnerability | Severity | Affected | Fix | Published |
|---|---|---|---|---|
| Cross-site scripting (XSS) CVE-2026-2374 | High 7.2 | Up to 1.8.0 | Fixed in a later version (latest 1.8.1) | 28 May 2026 |
| Broken access control CVE-2022-2913 | Medium 4.3 | Before 1.7 | Fixed in 1.7 | 16 Sep 2022 |
Read the published descriptions
- CVE-2026-2374, 28 May 2026
- 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. CVE record
- CVE-2022-2913, 16 Sep 2022
- The Login No Captcha reCAPTCHA WordPress plugin before 1.7 doesn't check the proper IP address allowing attackers to spoof IP addresses on the allow list and bypass the need for captcha on the login screen. CVE record
What to do if you run Login No Captcha reCAPTCHA
If you run Login No Captcha reCAPTCHA, open WordPress and check the installed version in Plugins. Compare it with the affected versions in the vulnerability record. If a fixed version is available, take a current backup and update to that version or the latest supported release.
If no fixed version exists, consider disabling and removing the plugin or replacing it with a maintained alternative. After dealing with the affected software, check administrator users, unexpected file changes, redirects, unfamiliar pages and security logs for signs that the site may already have been altered.
Email me about new Login No Captcha reCAPTCHA vulnerabilities
Free. We email you when a new vulnerability is published for Login No Captcha reCAPTCHA, usually within minutes. Confirm by email; unsubscribe any time.
Focus on your business. We’ll take care of your website.
From everyday updates to ongoing care, we keep your website working.