Is Login No Captcha reCAPTCHA safe to use?

Laskyr does not give safety verdicts. No known unpatched vulnerabilities in the latest version (1.8.1). As of 2026-11-04. 2 issues are on record for older versions; version 1.8.1 or newer fixes all of them that state a fix. Keep Login No Captcha reCAPTCHA on the latest version (1.8.1) and remove it if you do not use it.

Which versions of Login No Captcha reCAPTCHA are vulnerable?

Known issues on record (newest first): Stored cross-site scripting (XSS) (1.8.0 and older, fixed in 1.8.1); Missing authorization check (older than 1.7, fixed in 1.7). The full list with sources is on this page.

What is the latest version of Login No Captcha reCAPTCHA?

1.8.1, according to wordpress.org (last updated 2026-05-26). It has 50,000+ active installs.

What should I do if my Login No Captcha reCAPTCHA is out of date?

Take a backup, then update it from Dashboard > Updates (or run wp plugin update login-recaptcha). If you cannot update right away, deactivate it until you can. If you think the site was already attacked, run a free scan at https://laskyr.com/scan.

Plugins · login-recaptcha · data as of 2026-11-04

Is Login No Captcha reCAPTCHA safe? Known vulnerabilities and latest version

Latest version: 1.8.1
Last updated: 2026-05-26
Active installs: 50,000+
Known issues on record: 2
Unpatched in latest: 0
Tested up to WP: 7.0.8 · PHP 7.4+

Adds a Google No Captcha ReCaptcha checkbox to your Wordpress and Woocommerce login, forgot password, and user registration pages. — by Robert Peake

What to do

Update to the latest version (1.8.1). Anything older than 1.8.1 has at least one known issue listed below. Dashboard → Updates, or Plugins → “update now”.
If you cannot update right away, deactivate it until you can.
Turn on auto-updates for it: Plugins → “Enable auto-updates” on its row.
If you ran a vulnerable version and something looks off (spam pages, strange admins, redirects), run the free scan.

With WP-CLI: wp plugin get login-recaptcha --field=version shows what you run; wp plugin update login-recaptcha updates it.

Check your version

Known vulnerabilities

2 on record, newest first. “Affected” is the version range the source gives; “fixed in” is the version the source names, or (marked *) the first wordpress.org release after the last affected version.

high 7.2 CVE-2026-2374 · published 2026-05-28

Stored cross-site scripting (XSS) in Login No Captcha reCAPTCHA (1.8.0 and older)

Affected: 1.8.0 and older
Fixed in: 1.8.1 *
Access needed (per CVSS): No login needed
Range from: CVE record (the advisory publisher) · score by Wordfence

Details from the advisory

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.

NVD CVE-2026-2374 Wordfence advisory Code change (fix)wordpress.org Plugin source

medium 4.3 CVE-2022-2913 · published 2022-09-16

Missing authorization check in Login No Captcha reCAPTCHA (older than 1.7)

Affected: older than 1.7
Fixed in: 1.7
Access needed (per CVSS): No login needed; someone on the site has to click a link or open a page
Range from: advisory text · score by NVD

Details from the advisory

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.

NVD CVE-2022-2913 WPScan advisory

Recent activity

2026-05-26 — latest release on wordpress.org (1.8.1).
2026-05-28 — Stored cross-site scripting (XSS) disclosed (CVE-2026-2374), fixed in 1.8.1.
2022-09-16 — Missing authorization check disclosed (CVE-2022-2913), fixed in 1.7.

Free. We check the CVE feeds every day and email you only when a new issue for Login No Captcha reCAPTCHA (login-recaptcha) is published or a fix ships. Unsubscribe in one click.

Browse vulnerabilities

Types found in this plugin: Cross-site scripting (XSS) (1) · Missing authorization (1)

Where this data comes from

Version, last update, installs: wordpress.org/plugins/login-recaptcha (Plugins API), fetched 2026-11-04.
Vulnerabilities: NIST National Vulnerability Database (NVD), checked 2026-11-04. This product uses data from the NVD API but is not endorsed or certified by the NVD.
Each record links to its CVE page and to the original advisory (Wordfence, Patchstack or WPScan) where there is one. We only list a CVE here when its references or its advisory name this exact plugin, so a few real issues may be missing; none should be about a different plugin. Spot an error? Email Daniel.

Badge for your site or docs (states facts with a date, not a verdict):

<a href="https://laskyr.com/plugins/login-recaptcha"><img src="https://laskyr.com/plugins/login-recaptcha/badge.svg" alt="Login No Captcha reCAPTCHA vulnerability status"></a>

← Check another plugin · Free hacked-site scan