HomeWordPress vulnerabilitiesLoginizer
Loginizer vulnerabilities
Loginizer has 6 known vulnerabilities in this database. The most recent published record is dated 5 Nov 2024.
- Known vulnerabilities
- 6
- Active installs
- 1m+
- Latest version
- 2.1.1
- Last updated
- 28 Sep 2026
- Most recent
- 5 Nov 2024
Find it in your WordPress dashboard under Plugins. Severity is based on the CVSS score published with the CVE where one is available.
| Vulnerability | Severity | Affected | Fix | Published |
|---|---|---|---|---|
| Authentication bypass CVE-2024-10097 | High 8.1 | Before 1.9.3 | Fixed in 1.9.3 | 5 Nov 2024 |
| Cross-site scripting (XSS) CVE-2023-2296 | Medium 6.1 | Before 1.7.9 | Fixed in 1.7.9 | 30 May 2023 |
| Cross-site scripting (XSS) CVE-2020-27615 | Critical 9.8 | Before 1.6.4 | Fixed in 1.6.4 | 21 Oct 2020 |
| Cross-site scripting (XSS) CVE-2018-11366 | Medium 6.1 | Up to 1.3.9 | Fixed in a later version (latest 2.1.1) | 22 May 2018 |
| SQL injection CVE-2017-12650 | Critical 9.8 | Up to 1.3.5 | Fixed in a later version (latest 2.1.1) | 7 Aug 2017 |
| Cross-site request forgery (CSRF) CVE-2017-12651 | High 8.8 | Up to 1.3.5 | Fixed in a later version (latest 2.1.1) | 7 Aug 2017 |
Read the published descriptions
- CVE-2024-10097, 5 Nov 2024
- The Loginizer Security and Loginizer plugins for WordPress are vulnerable to authentication bypass in all versions up to, and including, 1.9.2. This is due to insufficient verification on the user being returned by the social login token. This makes it possible for unauthenticated attackers to log in as any existing user on the site, such as an administrator, if they have access to the email and the user does not have an already-existing account for the service returning the token. CVE record
- CVE-2023-2296, 30 May 2023
- The Loginizer WordPress plugin before 1.7.9 does not escape a parameter before outputting it back in the page, leading to a Reflected Cross-Site Scripting which could be used against high privilege users such as admin CVE record
- CVE-2020-27615, 21 Oct 2020
- The Loginizer plugin before 1.6.4 for WordPress allows SQL injection (with resultant XSS), related to loginizer_login_failed and lz_valid_ip. CVE record
- CVE-2018-11366, 22 May 2018
- init.php in the Loginizer plugin 1.3.8 through 1.3.9 for WordPress has Unauthenticated Stored Cross-Site Scripting (XSS) because logging is mishandled. This is fixed in 1.4.0. CVE record
- CVE-2017-12650, 7 Aug 2017
- SQL Injection exists in the Loginizer plugin before 1.3.6 for WordPress via the X-Forwarded-For HTTP header. CVE record
- CVE-2017-12651, 7 Aug 2017
- Cross Site Request Forgery (CSRF) exists in the Blacklist and Whitelist IP Wizard in init.php in the Loginizer plugin before 1.3.6 for WordPress because the HTTP Referer header is not checked. CVE record
What to do if you run Loginizer
If you run Loginizer, open WordPress and check the installed version in Plugins. Compare it with the affected versions in the vulnerability record. If a fixed version is available, take a current backup and update to that version or the latest supported release.
If no fixed version exists, consider disabling and removing the plugin or replacing it with a maintained alternative. After dealing with the affected software, check administrator users, unexpected file changes, redirects, unfamiliar pages and security logs for signs that the site may already have been altered.
Email me about new Loginizer vulnerabilities
Free. We email you when a new vulnerability is published for Loginizer, usually within minutes. Confirm by email; unsubscribe any time.
Focus on your business. We’ll take care of your website.
From everyday updates to ongoing care, we keep your website working.