What is the severity of CVE-2022-2913?

CVE-2022-2913 is classified as a critical vulnerability due to the potential for unauthorized access to the login system.

How do I fix CVE-2022-2913?

To fix CVE-2022-2913, you should update the Login No Captcha reCAPTCHA WordPress plugin to version 1.7 or later.

Who is affected by CVE-2022-2913?

CVE-2022-2913 affects users of the Login No Captcha reCAPTCHA plugin for WordPress versions prior to 1.7.

What type of attack does CVE-2022-2913 allow?

CVE-2022-2913 allows attackers to spoof allowed IP addresses and bypass the CAPTCHA verification on the login screen.

Is CVE-2022-2913 being actively exploited?

There is currently no publicly available information indicating that CVE-2022-2913 is being actively exploited in the wild.

Vulnerability/
CVE-2022-2913

medium

4.3

CWE

639

16/9/2022

3/8/2024

CVE-2022-2913: Login No Captcha reCAPTCHA < 1.7 - IP Check Bypass

First published: Fri Sep 16 2022(Updated: )

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.

Credit: contact@wpscan.com

Affected Software	Affected Version	How to fix
Google reCAPTCHA	<1.7

Remedy

https://wpscan.com/vulnerability/5231ac18-ea9a-4bb9-af9f-e3d95a3b54f1

Never miss a vulnerability like this again

Reference Links

https://wpscan.com/vulnerability/5231ac18-ea9a-4bb9-af9f-e3d95a3b54f1

Frequently Asked Questions

What is the severity of CVE-2022-2913?
CVE-2022-2913 is classified as a critical vulnerability due to the potential for unauthorized access to the login system.
How do I fix CVE-2022-2913?
To fix CVE-2022-2913, you should update the Login No Captcha reCAPTCHA WordPress plugin to version 1.7 or later.
Who is affected by CVE-2022-2913?
CVE-2022-2913 affects users of the Login No Captcha reCAPTCHA plugin for WordPress versions prior to 1.7.
What type of attack does CVE-2022-2913 allow?
CVE-2022-2913 allows attackers to spoof allowed IP addresses and bypass the CAPTCHA verification on the login screen.
Is CVE-2022-2913 being actively exploited?
There is currently no publicly available information indicating that CVE-2022-2913 is being actively exploited in the wild.

agent/type
agent/softwarecombine
collector/mitre-cve
source/MITRE
agent/last-modified-date
agent/author
agent/title
agent/severity
agent/references
agent/remedy
agent/weakness
agent/first-publish-date
agent/event
agent/description
agent/source
agent/tags
collector/nvd-index
agent/software-canonical-lookup-request
vendor/login no captcha recaptcha project
canonical/google recaptcha

Company

Resources

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co

By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.

Frequently Asked Questions

What is the severity of CVE-2022-2913?
CVE-2022-2913 is classified as a critical vulnerability due to the potential for unauthorized access to the login system.
How do I fix CVE-2022-2913?
To fix CVE-2022-2913, you should update the Login No Captcha reCAPTCHA WordPress plugin to version 1.7 or later.
Who is affected by CVE-2022-2913?
CVE-2022-2913 affects users of the Login No Captcha reCAPTCHA plugin for WordPress versions prior to 1.7.
What type of attack does CVE-2022-2913 allow?
CVE-2022-2913 allows attackers to spoof allowed IP addresses and bypass the CAPTCHA verification on the login screen.
Is CVE-2022-2913 being actively exploited?
There is currently no publicly available information indicating that CVE-2022-2913 is being actively exploited in the wild.