Clean Login at a glance
- 9 publicly disclosed vulnerabilities, 2 of them rated High or Critical. The most recent was disclosed on Oct 27, 2026.
- Ranked #2985 by popularity on WordPress.org (5,000+ active installs).
- The latest version is 2.0.3 (released Nov 16, 2026). The most recent security fix shipped in 1.21.
- Every disclosed vulnerability has a fix. If you are on the latest version, none of them apply to you.
- The first thing to do: update to the latest version and turn on automatic updates.
Check your Clean Login version
Enter the Clean Login version number shown on your Plugins screen to see only the vulnerabilities that apply to it, most serious first.
Your version number is compared on this page only. It is not sent anywhere.
Get an email when a new vulnerability is disclosed
We'll tell you when a new vulnerability is disclosed in “Clean Login”, with the version that fixes it. Free, email address only, stop any time.
We use your email address only for these alerts. Privacy policy
Want every plugin and theme on your site checked daily?
With Security Ready Standard, just install the “KazLinks Security Ready” plugin from WordPress.org. It sends only the names and versions of your plugins and themes, and we check them against disclosed vulnerabilities every day. Your first in-depth scan is free.
How to check whether your site is affected
- 1
Find your version
In your WordPress dashboard, open Plugins → Installed Plugins and look at the version number under “Clean Login”.
- 2
Compare it with the list below
If your version falls within “Affected versions”, that vulnerability applies to you. If you are on the “Fixed in” version or later, it does not.
- 3
Update
Click “Update now” to move to the latest version (2.0.3). Taking a backup first is a good idea.
- 4
Turn on automatic updates
On the same screen, click “Enable auto-updates” so future fixes are installed automatically.
Known Clean Login vulnerabilities
Clean Login <= 1.20.1 - Missing Authorization to Authenticated (Contributor+) Arbitrary Clean-Login Option Update via 'save_post' Hook
Missing authorization · CVE-2026-116610
Affected versions: ≤ 1.20.1
Fixed in: 1.21
Severity: Medium 4.3 · Disclosed Oct 27, 2026
Clean Login <= 1.18 - Unauthenticated CAPTCHA Bypass
Other weakness · CVE-2026-90977
Affected versions: ≤ 1.18
Fixed in: 1.19
Severity: Medium 5.3 · Disclosed Sep 16, 2026
Clean Login <= 1.18 - Unauthenticated Account Registration
Missing authorization · CVE-2026-90976
Affected versions: ≤ 1.18
Fixed in: 1.19
Severity: Medium 5.3 · Disclosed Sep 16, 2026
Clean Login <= 1.15 - Unauthenticated Insecure Direct Object Reference
Missing authorization · CVE-2026-54184
Affected versions: ≤ 1.15
Fixed in: 1.16
Severity: Medium 5.3 · Disclosed Jun 16, 2026
Clean Login <= 1.14.5 - Authenticated (Contributor+) Local File Inclusion
Arbitrary file read or deletion · CVE-2024-8252
Affected versions: ≤ 1.14.5
Fixed in: 1.14.6
Severity: High 8.8 · Disclosed Aug 29, 2024
Clean Login <= 1.13.6 - Authenticated (Contributor+) Stored Cross-Site Scripting via Shortcode
Cross-site scripting (XSS) · CVE-2022-4838
Affected versions: ≤ 1.13.6
Fixed in: 1.13.7
Severity: Medium 6.4 · Disclosed Jan 10, 2023
Clean Login 1.12.6.3 - Cross-Site Scripting
Cross-site scripting (XSS)
Affected versions: ≥ 1.12.6.3, ≤ 1.12.6.3
Fixed in: 1.12.6.4
Severity: Medium 6.1 · Disclosed Aug 9, 2021
Clean Login <= 1.10.3 - Cross-Site Request Forgery
Cross-site request forgery (CSRF) · CVE-2017-8875
Affected versions: ≤ 1.10.3
Fixed in: 1.10.4
Severity: High 8.8 · Disclosed Jun 29, 2020
Clean Login <= 1.5 - Reflected Cross-Site Scripting
Cross-site scripting (XSS) · CVE-2015-9336
Affected versions: ≤ 1.5
Fixed in: 1.5.1
Severity: Medium 6.1 · Disclosed Jul 27, 2015
| Vulnerability | Affected versions | Fixed in | Severity | Disclosed |
|---|---|---|---|---|
| Clean Login <= 1.20.1 - Missing Authorization to Authenticated (Contributor+) Arbitrary Clean-Login Option Update via 'save_post' HookMissing authorization · CVE-2026-116610 | ≤ 1.20.1 | 1.21 | Medium 4.3 | Oct 27, 2026 |
| Clean Login <= 1.18 - Unauthenticated CAPTCHA BypassOther weakness · CVE-2026-90977 | ≤ 1.18 | 1.19 | Medium 5.3 | Sep 16, 2026 |
| Clean Login <= 1.18 - Unauthenticated Account RegistrationMissing authorization · CVE-2026-90976 | ≤ 1.18 | 1.19 | Medium 5.3 | Sep 16, 2026 |
| Clean Login <= 1.15 - Unauthenticated Insecure Direct Object ReferenceMissing authorization · CVE-2026-54184 | ≤ 1.15 | 1.16 | Medium 5.3 | Jun 16, 2026 |
| Clean Login <= 1.14.5 - Authenticated (Contributor+) Local File InclusionArbitrary file read or deletion · CVE-2024-8252 | ≤ 1.14.5 | 1.14.6 | High 8.8 | Aug 29, 2024 |
| Clean Login <= 1.13.6 - Authenticated (Contributor+) Stored Cross-Site Scripting via ShortcodeCross-site scripting (XSS) · CVE-2022-4838 | ≤ 1.13.6 | 1.13.7 | Medium 6.4 | Jan 10, 2023 |
| Clean Login 1.12.6.3 - Cross-Site ScriptingCross-site scripting (XSS) | ≥ 1.12.6.3, ≤ 1.12.6.3 | 1.12.6.4 | Medium 6.1 | Aug 9, 2021 |
| Clean Login <= 1.10.3 - Cross-Site Request ForgeryCross-site request forgery (CSRF) · CVE-2017-8875 | ≤ 1.10.3 | 1.10.4 | High 8.8 | Jun 29, 2020 |
| Clean Login <= 1.5 - Reflected Cross-Site ScriptingCross-site scripting (XSS) · CVE-2015-9336 | ≤ 1.5 | 1.5.1 | Medium 6.1 | Jul 27, 2015 |
Vulnerability data: Wordfence Intelligence (Copyright Defiant, Inc. · license terms). Severity is the CVSS score (0–10). Most recent disclosure: Oct 27, 2026.
Most common weaknesses in Clean Login
Missing authorization
3 issues
Actions that should require a login or a particular role can be carried out without the proper check. Attackers use this to change settings or read data they should not see.
Cross-site scripting (XSS)
3 issues
An attacker plants a malicious script on a page so that it runs in visitors’ browsers. If an administrator opens that page, the attacker can steal their session or act as the administrator.
Arbitrary file read or deletion
1 issue
An attacker can read or delete files on the server. Deleting a configuration file can take the site offline, and reading one can expose passwords.
Frequently asked questions
Is Clean Login safe to use?
Clean Login is a well-known plugin with 5,000+ active installs. Finding vulnerabilities in popular plugins is common, and most of them are fixed in newer versions. The important thing is to stay on the latest version (2.0.3) and turn on automatic updates.
How do I find which version of Clean Login my site is running?
In your WordPress dashboard, go to Plugins → Installed Plugins. The version number is shown under the plugin name. If you see “There is a new version available”, you are on an older version.
Could updating break my site?
Occasionally an update changes how something looks or works, so take a backup before updating. If an agency or developer maintains your site, send them a link to this page and ask them to update.
Can I check all my other plugins too?
Yes. Security Ready reads the versions of every plugin and theme on your site, matches them against known vulnerabilities every day, and tells you what to fix. Your first in-depth scan is free.
Check every plugin and theme automatically, every day
Security Ready reads the versions of every plugin, theme and WordPress core on your site, matches them against known vulnerabilities every day, and tells you how to fix what it finds. Your first in-depth scan is free, and no payment details are needed.
Think your site has already been hacked? Before updating, read what to do in the first hour. Updating alone does not remove a backdoor that has already been planted.