Login No Captcha reCAPTCHA <= 1.6.11 - CAPTCHA Bypass via Whitelisted IP Address Spoofing
Strategic Overview
- Status
- Patched in 1.7
- Affected Plugin
- Login No Captcha reCAPTCHA
- Affected Version
<= 1.6.11- CVSS
- 5.3Medium
- Weakness type
- CWE-285 · Improper Authorization
- CVE
CVE-2022-2913
At a glance
CVE-2022-2913 is a medium-severity Improper Authorization vulnerability in the Login No Captcha reCAPTCHA WordPress plugin, affecting versions <= 1.6.11. It carries a CVSS score of 5.3 (reachable over the network; low attack complexity). Exploitation requires no authentication. The issue is fixed in version 1.7; sites on affected versions should update now. Disclosed August 2022, reported by Daniel Ruf.
Vulnerability Overview
The Login No Captcha reCAPTCHA plugin for WordPress is vulnerable to CAPTCHA bypass in versions up to, and including, 1.6.11. This is due to the whitelisted IP address functionality relying on user-supplied IP addresses from an HTTP Header. If an attacker can gain access to a whitelisted IP address they can spoof the request to come from one of those IP addresses using an HTTP header which would bypass any restrictions.
Technical Analysis
The vector marks this flaw as remotely reachable over the network, with low attack complexity — no special timing or configuration is needed, and no privileges on the target site, and no interaction from a victim user.
CWE-285: Improper Authorization
Reaching this weakness in Login No Captcha reCAPTCHA <= 1.6.11 takes a caller who can reach the endpoint. Improper authorization means a permission check exists but does not cover the case being exercised, so a caller who is allowed to do one thing is allowed to do a neighbouring thing as well.
A lower-privileged account performs an action reserved for a higher one, which on a multi-author or membership site means an ordinary user reaching administrative behaviour. For Login No Captcha reCAPTCHA the fix is 1.7: builds <= 1.6.11 are affected, anything from 1.7 onward is not.
Remediation
Update to version 1.7, or a newer patched version
How does WordSec protect against this?
Because it turns on account access, WordSec's login security is the relevant layer: role-based two-factor, captcha and brute-force limits raise the cost of getting the account this needs. None of that substitutes for the fix: Login No Captcha reCAPTCHA 1.7 closes this, and updating the plugin is the step that ends it.
- Login Security
- Alerts
External References
Related records
Other vulnerabilities in Login No Captcha reCAPTCHA
Vulnerability data © Defiant, Inc., provided under the Wordfence Intelligence T&C