Clean Login vulnerabilities

Plugin slug clean-login · 9 known vulnerabilities · latest disclosed 2026-10-27 · WordPress.org page

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

2 of 9 rated high or critical (CVSS 7 or more).

Known vulnerabilities in Clean Login

SeverityAffected versionsFixed inCVEPublishedDetails
Medium 4.3<= 1.20.11.21CVE-2026-1166102026-10-27Advisory
Medium 5.3<= 1.181.19CVE-2026-909772026-09-16Advisory
Medium 5.3<= 1.181.19CVE-2026-909762026-09-16Advisory
Medium 5.3<= 1.151.16CVE-2026-541842026-06-16Advisory
High 8.8<= 1.14.51.14.6CVE-2024-82522024-08-29Advisory
Medium 6.4<= 1.13.61.13.7CVE-2022-48382023-01-10Advisory
Medium 6.11.12.6.31.12.6.4none2021-08-09Advisory
High 8.8<= 1.10.31.10.4CVE-2017-88752020-06-29Advisory
Medium 6.1<= 1.51.5.1CVE-2015-93362015-07-27Advisory

Check if a site is affected

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

Questions

Is the Clean Login plugin safe to use?

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

How do I check which version of Clean Login 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