Update this morning, Captcha not working

The last update had a fix for a vulnerability in the captcha feature.

Now for your situation….
To get back into your site simply FTP to your server and traverse to the wp-contents/plugins folder and rename the following folder from:

all-in-one-wp-security-and-firewall

to

all-in-one-wp-security-and-firewall-temp

The above will deactivate this plugin and you will be able to login.
Once logged in to WordPress you can rename that folder back and then disable the captcha feature for now.

Another thing to do is to clear all page caches from your server if you are using a caching plugin.
If you are hosting with WPengine or similar hosts who cache the login page can you please ask them to refresh the cache for your login page.

Hi, thank you for the response and I had already figured out how to change the plug-in folder file name and luckily the site was able to function. Unfortunately when I change the name back, it keeps all the old data and immediately logs me out because it has been more than 60 minutes. Should i just reinstall the plug-in you think?

I think clearing the configuration should work for you.

Log into your DB using PHPMyAdmin and go to the wp_options table and look for the option_name called aio_wp_security_configs.

When you locate this, just delete the whole row entry.
Then deactivate and reactivate the AIOWPS plugin and it will automatically reset all the settings to default values.
(Note: you will need to then reconfigure your aiowps settings again to however you wish)

I’m having the same problem with capture (not recognizing the answers given as correct). I’m not exactly sure what you are saying–is there a problem/bug with the plugin since the update that is causing this?

Or are you saying that it is a caching problem and not a plugin problem? If so, why would that have become an issue with the update when it was no problem prior to the update?

I just want to be able to understand exactly what’s going on here.

@jkisha,
The caching thing was just a hunch but because I have yet to physically see this problem occurring I can’t be 100% sure why you are seeing this issue.
All my sites don’t have the issue you are seeing.

I would like to see your login page using firebug – can you either post it here or contact me using my form?

OR, can you inspect the captcha field using firebug/developer tools and tell me whether or not you see a hidden input field with “name=aiowps-captcha-string-info“?

(we removed this field in the latest release)

having the same problem but I am not this savy….aie

We run 120+ websites all with the same issue. Started this morning.

I’m having this issue too. If it helps, I’m on Mac and Firefox gives the error (no visible captcha) but Chrome seems fine.

Here’s a link to my site. The captcha has been disabled in the plugin.
https://www.mudskippercafe.com
It’s hosted on Windows 2012 R2 IIS 8.5

One other point of interest. I had forgotten all about the plugin option for using captcha on the registration page and consequently didn’t disable it there. This morning I had a person register successfully after which I went to the site and tested the registration myself. It is working just fine on the registration page.

I’m having this same problem, but it occurred right after I turned on the “firewall” portion today on a site that previously didn’t have it turned on. And then, it outright doesn’t even SHOW the CAPTCHA field on Chrome, but fails login because “answer is incorrect” (I did an F12 inspect, and I don’t even see it as a hidden field). The field shows up in FireFox, but the answer is never accepted as correct. So I’ve disabled the plugin and am getting ready to just reset all the settings as you were talking about directly in the database, but I just wanted to add that yes, this is a thing that happened to me too today.

We are doing to do another release tomorrow with an enhancement to the captcha feature that will address this.

In the meantime, if you are having a big issue with this feature, please temporarily deactivate it.

The new update v4.1.4 should be better. Please try it.

Just want to say, “Thank you!” for being so pro-active!
Update is perfect.
You guys rock!

Thanks. That update seems to have fixed the problem.

Good to hear that.