GPLClub
🔌 Plugin

Loginizer Pro WordPress Plugin

v2.1.3 · Updated 31 Oct 2026 · Official site

Antivirus scan

Powered by ClamAV

✅ Verified clean

This product file has passed our security filters.

Want to run a fresh ClamAV scan right now? Takes a few seconds and shows scanner version, signature DB and live result.

This can take 5 to 30 seconds.

✓ !

Clean file Threat detected

No threats detected in this file.

File
Size
Scanned
ClamAV
Signature database

⚡ Powered by ClamAV

!

Scan could not be completed

Report product

If you detected an issue (broken file, malware, inappropriate content, etc.) let us know and we'll review it ASAP.

Sign in to report
Loginizer Pro WordPress Plugin · Plugin for WordPress
Follow

About Loginizer Pro WordPress Plugin

WordPress has more than one door, and some come open

Whoever worries about brute force attacks thinks of the login screen, wp-login.php. They set a limit on attempts, maybe a captcha, and consider the matter closed. But it is not the only entrance.

The xmlrpc.php file, which comes open by default in WordPress, is another route for brute force, and pingbacks are one more door, exposed to denial of service attacks. Protecting the form while leaving the other entrances open is locking the front door with the window open.

Loginizer Pro is built for that full inventory: limiting attempts, but also disabling or renaming XML-RPC, cutting off pingbacks, changing the address of the login and the admin area, and asking for a second factor.

What Loginizer Pro protects

  • Brute force: automatic IP lockout after a maximum number of failures, with recommended values already configured.
  • Two-factor authentication by email or app, and passwordless login with a link sent by email.
  • Challenge question and captcha with reCAPTCHA v2 or v3, hCaptcha or Cloudflare Turnstile.
  • Address change for wp-login.php and wp-admin.
  • XML-RPC and pingbacks: disable or rename XML-RPC and cut off pingbacks.
  • Country blocking, IP blacklist and whitelist and an automatic username blacklist.
  • MD5 checksum of core files, to know whether someone changed them.
  • Social login with Google, Facebook, X, GitHub, LinkedIn or Discord, also on WooCommerce, plus logs and email alerts.

The risk of locking up well: locking yourself out

Every layer you add to the login is also a new way to lock yourself out: the two-factor phone that gets lost, the renamed address nobody wrote down, the office IP locked after several failures.

The ways out exist, and it pays to know them first. If you get locked out, you rename the plugin folder to loginizer.bak over FTP or with the file manager. If the wp-admin change locks you out, it is enough to create a reset_admin.txt file in the Loginizer Pro folder. Two-factor authentication has its own procedure for disabling it by hand.

The whitelist is the other safety net: trusted IPs are not locked out when logging in, so your office one should be on it from day one.

What Loginizer does not watch

It is neither a firewall nor a malware scanner. It protects the entrance and checks the core, but its features do not include checking themes or plugins for malicious code, nor analysing requests to the rest of the site.

It does not make backups, and the captcha and social login depend on third parties, Google, hCaptcha, Cloudflare or each social network, each configured one by one.

Installing Loginizer Security without locking yourself out

The Pro version is a separate plugin called Loginizer Security. The free version of Loginizer needs WordPress 3.0 or later and PHP 5.5 or later.

  1. Add your IP to the whitelist before hardening anything.
  2. Disable XML-RPC and pingbacks if you do not use them.
  3. Turn on two-factor authentication for administrators and note how to disable it.
  4. Change the login address and keep it where whoever needs it will find it.

Other ways to harden the login

For the form and the shop, Login Security Pro adds reCAPTCHA or Turnstile to the WooCommerce login, registration and checkout. Login Protection Limit Failed Login Attempts PRO lengthens each lockout after every failure and blocks by country.

To stop your WordPress looking like what bots search for, Hide My WP Ghost changes the paths of WordPress, plugins and themes. And with LoginPress Pro, its limit login attempts add-on adds that brake.

Questions about Loginizer Pro

How does it differ from the free version?

The free version covers brute force, lockouts, logs, alerts and IP lists. Pro adds two-factor authentication, passwordless login, captcha, a challenge question, address change, XML-RPC and pingbacks, country blocking, MD5 and social login.

What happens if I get locked out?

You rename the plugin folder over FTP or with the file manager. For the wp-admin change there is also the reset_admin.txt file.

Which captchas does it support?

reCAPTCHA v2 and v3, hCaptcha and Cloudflare Turnstile, with the option of using recaptcha.net where Google is not available.

Does it replace a full security plugin?

No. It focuses on the login and on checking the core; to analyse traffic and scan themes and plugins you need another tool.

Topics

Version history

  • v
    2.1.3 Current 31 Oct 2026
  • v
    2.1.1 30 Sep 2026
  • v
    2.1.0 5 Sep 2026
  • v
    2.0.9 6 Aug 2026
  • v
    2.0.7 18 Apr 2026

Customer reviews

Sign in to leave a review. Only people who have the product can review it.

No reviews for this product yet.

Frequently asked questions

  • GPL (General Public License) is the license under which WordPress and most premium plugins/themes are distributed. It grants you the right to use, modify and redistribute the software in as many projects as you want, with no domain restrictions.

  • Yes. With membership you get automatic updates via our GPLClub Updater plugin (installed on your WP, detects new versions and applies them). With individual purchase, you get one year of manual updates from your account.

  • Depends on the plan. Monthly: 3 domains. Semi-annual: 7. Annual and Lifetime: 15. Individual purchase: 1 domain.

  • GPLClub offers its own support for installation, configuration and compatibility. For direct support from the original author (feature requests, product-specific bugs), a license purchased from the author is required.