Loginizer vulnerabilities

Plugin slug loginizer · 8 known vulnerabilities · latest disclosed 2024-11-04 · WordPress.org page

Every listed vulnerability has a fix. Version 1.9.3 or later is not affected by any of them. If your site runs an older version, update it.

4 of 8 rated high or critical (CVSS 7 or more).

Known vulnerabilities in Loginizer

SeverityAffected versionsFixed inCVEPublishedDetails
High 8.1<= 1.9.21.9.3CVE-2024-100972024-11-04Advisory
Medium 6.1<= 1.7.81.7.9CVE-2023-22962023-05-02Advisory
Medium 4.3< 1.7.61.7.6CVE-2022-450792022-12-05Advisory
Medium 6.1<= 1.7.51.7.6CVE-2022-450842022-05-12Advisory
Critical 9.8< 1.6.41.6.4CVE-2020-276152020-10-21Advisory
Medium 6.11.3.8 to 1.3.91.4.0CVE-2018-113662018-05-22Advisory
Critical 9.8< 1.3.61.3.6CVE-2017-126502017-08-08Advisory
High 8.8< 1.3.61.3.6CVE-2017-126512017-08-08Advisory

Check if a site is affected

Enter a site address to see which version of Loginizer and other plugins it runs, and whether they match a known vulnerability.

Questions

Is the Loginizer plugin safe to use?

All 8 known issues are fixed in current versions (1.9.3 or later). Keeping it updated is what matters.

How do I check which version of Loginizer my site runs?

In WordPress go to Plugins > Installed Plugins. From the outside, the free PluginPeek scan below reads the version from the site's public files.

How do I fix a vulnerable plugin?

Make a full backup, then update it from Dashboard > Updates and check the site afterwards. If you would rather not, we can do it for a fixed $99, paid after you have checked the site.

Check any WordPress site in one click while you browse: Add PluginPeek to Chrome