I’m getting a Fatal Error with WP Security Pro 4.3.2. It makes the Admin Dashboard total unusable, although the frontend of the website looks fine. See error log below. It first happened to me on May 11, but I hadn’t tried to login to the dashboard in a few weeks, so I wouldn’t have noticed earlier. When I manually remove WP Security Pro from the plugins folder, the issue resolves. The Admin Dashboard comes back if I reinstall and reactivate the plugin. I am running WordPress 6.1.1. The only change I can see that happened recently is that the default WordPress Theme Twenty-Twenty-Three updated itself automatically in March.
[12-May-2023 00:48:53 UTC] PHP Fatal error: Uncaught TypeError: chr(): Argument #1 ($codepoint) must be of type int, string given in /home/amyritterbusch/public_html/wp/wp-content/plugins/wp-security-pro/handler/login.php:45
Stack trace:
#0 /home/amyritterbusch/public_html/wp/wp-content/plugins/wp-security-pro/handler/login.php(45): chr()
#1 /home/amyritterbusch/public_html/wp/wp-includes/class-wp-hook.php(308): Mo_wp_LoginHandler->mo_wpns_init()
#2 /home/amyritterbusch/public_html/wp/wp-includes/class-wp-hook.php(332): WP_Hook->apply_filters()
#3 /home/amyritterbusch/public_html/wp/wp-includes/plugin.php(517): WP_Hook->do_action()
#4 /home/amyritterbusch/public_html/wp/wp-settings.php(617): do_action()
#5 /home/amyritterbusch/public_html/wp/wp-config.php(193): require_once('/home/amyritter...')
#6 /home/amyritterbusch/public_html/wp/wp-load.php(50): require_once('/home/amyritter...')
#7 /home/amyritterbusch/public_html/wp/wp-blog-header.php(13): require_once('/home/amyritter...')
#8 /home/amyritterbusch/public_html/wp/index.php(17): require('/home/amyritter...')
#9 {main}
thrown in /home/amyritterbusch/public_html/wp/wp-content/plugins/wp-security-pro/handler/login.php on line 45
When upgrading to 4.3 or 4.3.1 we get the following error on the /wp-admin/ backend:
TypeError thrown
chr(): Argument #1 ($codepoint) must be of type int, string given
The site is completely unusable from the Admin Dashboard. I have reverted to WP Security Pro 4.1.1 which seems to still work fine for us.
I think it may be a conflict with WooCommerce, but I’m not sure.
When we first got the TypeError I disabled all plugins and turned them back on one at a time, that is when I determined that only WP Security Pro was causing the error. And reverting to the earlier version of WP Security Pro 4.1.1 solved the problem.
I hope you can fix this in a future release. Thanks!
]]>After I have enabled the plugin and firewall I notice that the checkout button on woocommerce checkout page is disabled. If I disable the firewall it works perfectly.
Any ideas?
chr() expects parameter 1 to be int, string given 1 +
wp-content/plugins/wp-security-pro/handler/login.php:62
Getting this PHP Notice when activate the Plugin.
]]>I am currently using your country blocking feature but I don’t know how does it work i.e how do I get assure that the country that I selected is blocked?
Plus in your Web Application Firewall is see you provide security on 2 levels, what is the difference between the given 2 levels.
You provide a backup feature in your plugin, what is the use of this feature? It looks like it is useful.
Guy!
This is serious security error in your plugin.
You have to fix it immediately.
This plugin allows you to log in without a correct password when I Enable Google reCAPTCHA for login form.
I’m serious.
I wanted to protect myself against brute force, so I found this plugin in repo, I installed them and then I tested various features, i.a. Google reCaptcha (I had Login No Captcha reCAPTCHA before). So, in order to have everything in one place, I deactivated previous reCatpcha so that this function would be in this plugin.
I was surprised when I was attempt to check the functionality I finally entered not random login but my login and password (by pressing random keys from the keyboard) and here on my surprise the password worked?
Seriously?
To be sure, I checked it again, on another browser (and mobile), but this time only with Google reCaptcha enable.
the same.
Think about it:
If someone will know my (admin) login, all they need to do is being verified by reCAPTCH, with random password and voilà, they can do whatever they like.
Hello, how to delete or disable all login and error reports?
]]>Hi,
I installed the plugin and everything was working fine for about one week. Then suddenly it started giving 403 Forbidden errors for all users on all pages. Eventually figured out it was this plugin by disabling it via a change in the plugin directory name.
Any ideas on what could be causing this?
Thanks, -d
]]>hi,
there is a conflict between “WP Security Pro” and the Twitter add on from “All-in-One Event Calendar” can you fix this?
]]>