WordPress plugin
Loginizer security & vulnerabilities
No known unpatched vulnerabilities in the latest version
All 8 known vulnerabilities are fixed in the latest release. If you run an older version, update to null or newer.
- Critical2
- High2
- Medium4
- Low0
All Loginizer vulnerabilities
| Severity | Vulnerability | CVE | Published |
|---|---|---|---|
| High8.1 | Authentication Bypass via WordPress.com OAuth provider ≤1.9.2Update to 1.9.3 | CVE-2024-10097 | |
| Critical9.8 | SQL Injection <1.6.4Update to 1.6.4 | CVE-2020-27615 | |
| High8.8 | Cross-Site Request Forgery <1.3.6Update to 1.3.6 | CVE-2017-12651 | |
| Critical9.8 | Blind SQL Injection <1.3.6Update to 1.3.6 | CVE-2017-12650 |
- High8.1Authentication Bypass via WordPress.com OAuth provider
≤1.9.2Update to 1.9.3
- Critical9.8SQL Injection
<1.6.4Update to 1.6.4
- High8.8Cross-Site Request Forgery
<1.3.6Update to 1.3.6
- Critical9.8Blind SQL Injection
<1.3.6Update to 1.3.6
Loginizer: common questions
Does Loginizer have known vulnerabilities?
Yes. VulnCrest Radar lists 8 known vulnerabilities in Loginizer: 2 critical, 2 high, 4 medium. None are known to affect version null.
How do I check which version of Loginizer I run?
In wp-admin open Plugins → Installed Plugins; the version is shown under the name. Without admin access, our passive Check my site tool can often read it from public files.
What is the most recent Loginizer vulnerability?
CVE-2024-10097, published Nov 4, 2024: Loginizer Security and Loginizer <= 1.9.2 - Authentication Bypass via WordPress.com OAuth provider. Severity: High (CVSS 8.1).
Is any Loginizer vulnerability listed in CISA KEV?
No. None of the known Loginizer vulnerabilities is currently listed in the CISA KEV catalog.
