HomeWordPress vulnerabilitiesClean Login
Clean Login vulnerabilities
Clean Login has 6 known vulnerabilities in this database. The most recent published record is dated 18 Sep 2026.
- Known vulnerabilities
- 6
- Active installs
- 5,000+
- Latest version
- 1.19
- Last updated
- 15 Sep 2026
- Most recent
- 18 Sep 2026
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 |
|---|---|---|---|---|
| Broken access control CVE-2026-90976 | Medium 5.3 | Before 1.19 | Fixed in 1.19 | 18 Sep 2026 |
| Security weakness CVE-2026-90977 | Medium 5.3 | Before 1.19 | Fixed in 1.19 | 18 Sep 2026 |
| File inclusion CVE-2024-8252 | High 8.8 | Before 1.14.6 | Fixed in 1.14.6 | 30 Aug 2024 |
| Cross-site scripting (XSS) CVE-2022-4838 | Medium 5.4 | Before 1.13.7 | Fixed in 1.13.7 | 6 Feb 2023 |
| Cross-site scripting (XSS) CVE-2015-9336 | Medium 6.1 | Before 1.5.1 | Fixed in 1.5.1 | 22 Aug 2019 |
| Cross-site request forgery (CSRF) CVE-2017-8875 | Medium 6.5 | Before 1.8 | Fixed in 1.8 | 10 May 2017 |
Read the published descriptions
- CVE-2026-90976, 18 Sep 2026
- The Clean Login WordPress plugin before 1.19 does not check whether user registration is enabled before creating an account in its registration handler, allowing unauthenticated users to create accounts even when the site has registration disabled. CVE record
- CVE-2026-90977, 18 Sep 2026
- The Clean Login WordPress plugin before 1.19 does not verify its registration CAPTCHA when the stored session value is empty, allowing unauthenticated users to bypass the anti-automation control on the registration form and create accounts without solving it. CVE record
- CVE-2024-8252, 30 Aug 2024
- The Clean Login plugin for WordPress is vulnerable to Local File Inclusion in all versions up to, and including, 1.14.5 via the 'template' attribute of the clean-login-register shortcode. This makes it possible for authenticated attackers, with Contributor-level access and above, to include and execute arbitrary files on the server, allowing the execution of any PHP code in those files. This can be used to bypass access controls, obtain sensitive data, or achieve code execution in cases where images and other “safe” file types can be uploaded and included. CVE record
- CVE-2022-4838, 6 Feb 2023
- The Clean Login WordPress plugin before 1.13.7 does not validate and escape some of its shortcode attributes before outputting them back in the page, which could allow users with a role as low as contributor to perform Stored Cross-Site Scripting attacks which could be used against high privilege users such as admins. CVE record
- CVE-2015-9336, 22 Aug 2019
- The clean-login plugin before 1.5.1 for WordPress has reflected XSS. CVE record
- CVE-2017-8875, 10 May 2017
- CSRF in the Clean Login plugin before 1.8 for WordPress allows remote attackers to change the login redirect URL or logout redirect URL. CVE record
What to do if you run Clean Login
If you run Clean Login, 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 Clean Login vulnerabilities
Free. We email you when a new vulnerability is published for Clean Login, 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.