elibeckz

@bordoni thank you. I ran a new scan and the vulnerability still shows, even after applying the update. I will wait until tomorrow to do new scan. Maybe it needs more time for the security plugin to catch up with the patch.

It looks like it does work for me. Perhaps I can send you credentials to log in to backend. Once there, you can activate and deactivate the plugin as you see the website on a separate tab. I could also send you a screen shot of the front webpage.

I was having a similar issue. After applying the reCaptcha keys, I would receive the “Failed to send your message. Please try later or contact the administrator by another method.” message enclosed in orange.
The issue’s root cause was that the contact page (where the form is) was being cached from the previous version, which conflicted somehow with the reCaptcha keys…a real mess.
The cache plugin being used in my case is W3 Total Cache. I added the contact page to the pages that should not be cached. (Dashboard > Performance > Page Cache) It seemed to have resolved the issue.

Ok,I think I was able to pinpoint the issue. The form would submit the information successfully as long as I was logged in to my WordPress account linked to the website. Once I logged out, the issue would reappear and the form would not work (I would get the “Failed to send… error in the orange border”). I suspected the issue had to do with the form being cached, which would mean that the form being brought to the website was the form from the previous Contact Form version, which conflicted with the new reCaptcha keys….a real mess. We use this W3 Total Cache plugin, so what I did was I added the contact web page to the list of pages I did not want to be cached. Here are the instructions on how to do it for this plugin https://www.redbridgenet.com/how-to-exclude-specific-pages-from-w3-total-cache/.
After this change was made, I was able to see the form working successfully from different browsers.

Ok,I think I was able to pinpoint the issue. The form would submit the information successfully as long as I was logged in to my WordPress account linked to the website. Once I logged out, the issue would reappear and the form would not work (I would get the “Failed to send… error in the orange border”). I suspected the issue had to do with the form being cached, which would mean that the form being brought to the website was the form from the previous Contact Form version, which conflicted with the new reCaptcha keys….a real mess. We use this W3 Total Cache plugin, so what I did was I added the contact web page to the list of pages I did not want to be cached. Here are the instructions on how to do it for this plugin https://www.redbridgenet.com/how-to-exclude-specific-pages-from-w3-total-cache/.

Hope it helps!

We are experiencing the same issue. It failed the first time, then the next day it worked. I try again today and the problem is back. I don’t know if it has to do with cache or something else. No solution has been received yet.

They problem is back again. For some reason the following is happening:
– I keep getting the error message “Failed to send your message. Please try later or contact administrator by another method.
– I deleted some of the text “These security checks to prevent unauthorised access to your account.” and recatpcha tag and the these changes were saved.Yet, the recaptcha tag text keeps showing on the website. So, the change is not reflected on the website but I see the change on the backdoor form template.Please help! Thanks.

Thanks for the prompt reply. From the article, it looks like the absence of wp_footer could be the issue. However, that is not the case in my issue. I can see wp_footer() in code footer.php from the Theme the page is built on. This morning I checked the page again and it seemed to work. I did not get the error message and the form submission was processed successfully. Also, the reCaptcha flag shows on many web pages (I haven’t checked them all), not just the home page. I think allowing some time (12 hours maybe)
– after applying the site key – for the changes to take effect is the solution in this case.