"Disable the default login error message" is not working

Bug Reports
1

Hi
when i check “Disable the default login error message” in setting, this error message still viewing on login form.

2

If the option “Disable the default login error message” is enabled but the message is still visible, it usually means that another plugin or your theme is overriding WordPress’ default authentication errors.

Try deactivating your theme and plugins. If WP Cerber works correctly after that, it means the variables are being loaded earlier in the stack or through theme/plugin hooks.
You can also do it in a more “brute force” but effective way.

Exemple Code rapyd rabbit

add_filter( ‘login_errors’, function( $error ){
‘’;
});

login_errors WordPress will no longer display any error messages.

Or

add_action( ‘wp_login_failed’, function( $username ){
wp_safe_redirect( wp_login_url() );
exit;
});

This prevents messages like “ERROR: Invalid username or password.” from being displayed.

or

add_filter( ‘authenticate’, function( $user, $username, $password ) {

if ( is_wp_error( $user ) ) {
    return new WP_Error( null, '' );
}

return $user;

}, 30, 3 );

This filter catches all errors before WordPress sends its message.

or

add_filter( ‘wp_login_errors’, function( $errors ){
if ( is_wp_error( $errors ) ) {
$errors->remove_all();
}
return $errors;
});

Clears all errors, including those injected by plugins.

These are only examples, even though the code is functional.
In summary, just because a WordPress plugin provides an option does not mean another plugin or theme isn’t overriding that function elsewhere.
And that is exactly a developer’s job: to understand how your own “recipe” is being cooked and what flavor it’s supposed to have.

In short, you have two choices:
either you bring out the heavy artillery and override the behavior directly in a MU-plugin or in your theme’s functions file, or you hire an expert who can solve it for you.

But understand this clearly: the issue is not WP Cerber.
The real problem is that your site as a whole is calling functions and variables from multiple places and unfortunately, one of them is overriding the error output, often for design or styling reasons.

:alien::v: