CVE-2022-2913VulnerabilityPublished 16 Sep 2022Updated 3 Jun 2025

CVE-2022-2913: Login No Captcha reCAPTCHA (WordPress plugin) · Insecure Direct Object Reference

Affects Login No Captcha reCAPTCHA (WordPress plugin)Source CVE Database V5

Not known to be exploited · CVSS 4.3 Medium · fixed in 1.7 : update Login No Captcha reCAPTCHA (WordPress plugin) when convenient.

Data as of 26 Oct 2026, 06:26 UTC

CVSS 3.1 base score

4.3Medium

How severe the flaw is on the 0–10 CVSS scale.

EPSS: 0.7% chance of exploitation in 30 days – higher than 54% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch: Available – fixed in 1.7

CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:L/A:N

Attack Vector: Network
Attack Complexity: Low
Privileges Required: None
User Interaction: Required
Scope: Unchanged
Confidentiality: None
Integrity: Low
Availability: None

Bold values are the worst case: easiest to exploit or largest impact.

Attack Vector: Network: The vulnerable component is bound to the network stack and the set of possible attackers extends beyond the other options listed, up to and including the entire Internet. Such a vulnerability is often termed 'remotely exploitable' and can be thought of as an attack being exploitable at the protocol level one or more network hops away (e.g., across one or more routers).
Attack Complexity: Low: Specialized access conditions or extenuating circumstances do not exist. An attacker can expect repeatable success against the vulnerable component.
Privileges Required: None: The attacker is unauthorized prior to attack, and therefore does not require any access to settings or files to carry out an attack.
User Interaction: Required: Successful exploitation of this vulnerability requires a user to take some action before the vulnerability can be exploited.
Scope: Unchanged: An exploited vulnerability can only affect resources managed by the same security authority. In this case, the vulnerable component and the impacted component are either the same, or both are managed by the same security authority.
Confidentiality: None: There is no loss of confidentiality within the impacted component.
Integrity: Low: Modification of data is possible, but the attacker does not have control over the consequence of a modification, or the amount of modification is limited. The data modification does not have a direct, serious impact on the impacted component.
Availability: None: There is no impact to availability within the impacted component.

Definitions: FIRST CVSS v3.1 specification.

Exploitation evidence

Disclosed: evidence found.
CVE published 16 Sep 2022
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 2026-10-26.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponised: Public exploit code exists in Metasploit or Exploit-DB, or CISA SSVC reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

What to do

Affected software

Product	Affected	Fixed in
Unknown Login No Captcha reCAPTCHA	Affected =1.7	Fixed in–

AI-suggested

European organizations should immediately verify if their WordPress installations use the Login No Captcha reCAPTCHA plugin and identify the version in use. If running a version prior to 1.7, they should upgrade to version 1.7 or later where the vulnerability is addressed. In the absence of an official patch, organizations can mitigate risk by disabling the allow list feature or restricting login attempts through alternative means such as web application firewalls (WAFs) that enforce IP reputation and rate limiting. Additionally, implementing multi-factor authentication (MFA) on WordPress logins can reduce the risk of unauthorized access even if CAPTCHA is bypassed. Monitoring login attempts for unusual patterns and enabling alerting on repeated failed logins can help detect exploitation attempts. Network-level controls should be applied to prevent IP spoofing where possible, such as ingress filtering on organizational networks. Finally, organizations should ensure that strong password policies are enforced to reduce the effectiveness of brute-force attacks facilitated by this vulnerability.

Description

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.

Impact

For European organizations using the Login No Captcha reCAPTCHA WordPress plugin, this vulnerability could facilitate automated or scripted login attempts by bypassing CAPTCHA protections. This increases the risk of brute-force attacks against user accounts, potentially leading to unauthorized access if weak passwords are used. While the vulnerability itself does not directly expose sensitive data or cause service disruption, it lowers the barrier for attackers to attempt credential stuffing or password guessing attacks. Organizations with public-facing WordPress sites that rely on this plugin for login security are at risk of increased attack surface. This is particularly concerning for sectors with sensitive user data or regulatory compliance requirements such as GDPR, where unauthorized access could lead to data breaches and legal consequences. The vulnerability may also be leveraged as a stepping stone in multi-stage attacks targeting European businesses, especially those with high-value accounts or administrative privileges protected by this plugin.

CWE-639Authorization Bypass Through User-Controlled Key (opens in a new tab)
Base weaknessLikelihood of exploit: HighCWE Top 25 (2025): #24OWASP Top 10 A01:2025: Broken Access Control (opens in a new tab)
The system's authorization functionality does not prevent one user from gaining access to another user's data or record by modifying the key value identifying the data.
Architecture and Design
For each and every data access, ensure that the user has sufficient privilege to access the record that is being requested.
Architecture and Design · Implementation
Make sure that the key that is used in the lookup of a specific user's record is not controllable externally by the user or that any tampering can be detected.
Architecture and Design
Use encryption in order to make it more difficult to guess other legitimate values of the key or associate a digital signature with the key so that the server can verify that there has been no tampering.
OWASP Cheat Sheets
Access Control (opens in a new tab)
Authorization Testing Automation (opens in a new tab)
Cross-Site Request Forgery Prevention (opens in a new tab)
Insecure Direct Object Reference Prevention (opens in a new tab)
Authorization (opens in a new tab)
OWASP ASVS 4.0.3
V4.1.2 (opens in a new tab)
V4.2.1 (opens in a new tab)
V8.3.8 (opens in a new tab)
From MITRE CWE, MITRE CAPEC and OWASP (Top 10, OpenCRE).

References

wpscan.com/vulnerability/5231ac18-ea9a-4bb9-af9f-e3d95a3b54f1 (opens in a new tab)

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 4 Jul 2025, 10:40 UTC

WeaknessesCWE-639

Technical details

References

Community reviews

Related threats