• Skip to primary navigation
  • Skip to main content
  • Skip to primary sidebar

RocketGeek

Home of WP-Members, The Original WordPress Membership Plugin

  • WordPress Plugins
    • WP-Members
      • FAQs
      • Quick Start
      • Documentation
      • Extensions
    • Advanced Options
      • Documentation
      • Purchase the Plugin
      • Get the Pro Bundle
    • Download Protect
      • Documentation
      • Purchase the Plugin
      • Get the Pro Bundle
    • Invite Codes
      • Documentation
      • Purchase the Plugin
      • Get the Pro Bundle
    • MailChimp Integration
      • Documentation
      • Purchase the Plugin
      • Get the Pro Bundle
    • PayPal Subscriptions
      • Documentation
      • Purchase the Plugin
      • Get the Pro Bundle
    • Salesforce Web-to-Lead
    • Security
      • Documentation
      • Purchase the Plugin
      • Get the Pro Bundle
    • Text Editor
      • Purchase the Plugin
      • Get the Pro Bundle
    • User List
      • Documentation
      • Purchase the Plugin
      • Get the Pro Bundle
    • User Tracking
      • Documentation
      • Purchase the Plugin
      • Get the Pro Bundle
    • Memberships for WooCommerce
    • WordPass
  • Blog
    • Basics
    • Tips and Tricks
    • Filters
    • Actions
    • Code Snippets
    • Shortcodes
    • Design
    • Release Announcements
  • Store
    • Cart
    • Checkout
  • Contact
  • Log In
  • Show Search
Hide Search
Home » Plugins » WP-Members » Documentation » FAQs » Why does reCAPTCHA v3 fail

Why does reCAPTCHA v3 fail

If you are using Google’s reCAPTCHA version 3 and it is generally always failing for the users, it is most likely due to the user’s “score.”

reCAPTCHA v3 is based on a user score. If users are being rejected based on the captcha (and assuming the API keys being used are for v3), they are being scored too low.

The plugin currently uses Google’s default of 0.5 as a necessary score to clear the captcha. (See: https://developers.google.com/recaptcha/docs/v3)

Changing the required score

There is not currently a filter hook in the plugin to change this value, but there will be one included in the next version (3.3.9).  If you want to use the upcoming filter now, you can replace the plugin’s file /includes/class-wp-members-captcha.php” with the version here.  Then you can apply the “wpmem_recaptcha_score” filter as follows:

add_filter( 'wpmem_recaptcha_score', function( $score ) {
    /*
     * Return a score between 1 and 0.1.
     * A lower score will let through more results.
     */
    return 0.3;
});

A better way

Captchas are an annoyance for users, and they are easily circumvented by malicious users, bots, and spammers.  If what you’re really trying to do is avoid spam registrations, there are far better methods than a captcha.

The plugin has a free extension that uses the stopforumspam.org API.  Using that alone will likely shut down your spam registration problem to near zero.

A surefire method of shutting down registration spam is to use a “honey pot.” This is a field the user doesn’t see, but a bot does. When we validate the form, if the honey pot field has data in it, the form was most likely completed by a bot or an automated user and is likely spam.  Premium support subscribers have access to a tutorial and code snippets on this site that will teach you how to implement a honey pot.

If you want the best of both worlds and a fair and reasonable price, the WP-Members Security extension provides you the stopforumspam.org API, the Akismet API, and a simple setting to enable a honey pot in the WP-Members registration form.  (It also includes a number of other great security features like login lockout and prevention of concurrent logins.)

  • Getting Started
  • Recommended WordPress® Settings
  • Plugin Settings
    • Options
    • Fields
    • Dialogs
    • Emails
    • New Feature Settings
  • Managing Content
    • Restricting Posts
    • Restricting Pages
    • Show Excerpts
    • Custom Post Types
  • Managing Users
    • Import Users
    • Export Users
    • Edit Users
    • Search Users
  • Login
  • Registration
    • Choosing Fields
    • Create a Registration Page
    • Moderating Registration
    • Using CAPTCHA
    • Removing Registration Options
  • User Profile
  • Memberships
    • Membership Properties
    • Membership Levels
  • Menus
    • Individual Menu Items
    • Logged In Menus
    • Login/Logout Menu Link
  • Customizing Emails
    • Email Address
    • Email Content
    • Email Format
    • Email Shortcodes
    • Email Troubleshooting
  • Customizing Forms
    • Create a Custom Stylesheet
    • Using the WordPress Customizer
    • Login Form HTML
    • Registration Form HTML
    • Widget Login Form HTML
  • Translation and Localization
    • Maintain a custom translation file
    • Filter untranslated strings
    • Multi-language Considerations
  • Shortcodes
    • Pages and Forms
    • Login Status
    • User Fields
    • Memberships
    • Email
    • Other Shortcodes
  • WP-CLI Commands
  • API Functions
  • Filter Hooks
  • Action Hooks
  • FAQs
    • Email troubleshooting
    • Passwords are not being included in Emails
    • The plugin isn’t blocking my content
    • Are files protected?
    • How can I prevent registration spam?
    • How to add a shortcode
    • How to apply login redirects
    • Why can’t users log in?
    • Why does reCAPTCHA v3 fail?
    • Troubleshooting Really Simple Captcha
    • Why do I get a 403 error?
    • How do I use code snippets?
    • My changes aren’t showing up
    • How to hide the “Admin Bar”
    • How to add a forgot password link
    • Password reset doesn’t show any fields
    • Domain not included in the password reset link
    • There was an error processing the form
    • Hidden vs. Restricted
  • Demo Videos
  • How to Request Support
  • Copy Settings for Support
  • Hosting Recommendations

Ready to get started?

Join Today!

© 2025 · butlerblog.com · RocketGeek is built using WordPress, WP-Members, and the Genesis Framework

  • butlerblog.com
  • WP-Members Support Subscription
  • Terms of Service
  • Privacy Policy
  • Refund Policy