Clean Login
by WordPress
Source repositories
CVEs (7)
| CVE | Vendor / Product | Sev | Risk | CVSS | EPSS | KEV | Published | Description |
|---|---|---|---|---|---|---|---|---|
| CVE-2024-8252 | Hig | 0.57 | 8.8 | 0.03 | Aug 30, 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… | ||
| CVE-2026-54184 | Hig | 0.53 | 8.2 | 0.00 | Jun 17, 2026 | Unauthenticated Insecure Direct Object References (IDOR) in Clean Login <= 1.15 versions. | ||
| CVE-2015-9336 | Med | 0.40 | 6.1 | 0.01 | Aug 22, 2019 | The clean-login plugin before 1.5.1 for WordPress has reflected XSS. | ||
| CVE-2022-4838 | Med | 0.35 | 5.4 | 0.01 | Feb 6, 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… | ||
| CVE-2026-90977 | Med | 0.34 | 5.3 | 0.00 | Sep 18, 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-2026-90976 | Med | 0.34 | 5.3 | 0.00 | Sep 18, 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-2026-116610 | Med | 0.21 | 4.3 | 0.00 | Oct 28, 2026 | The Clean Login plugin for WordPress is vulnerable to Missing Authorization in versions up to, and including, 1.20.1 due to a missing capability check on the CleanLogin_Shortcode::get_pages_with_shortcodes() function hooked to the save_post action. This makes it possible for… |
- risk 0.57cvss 8.8epss 0.03
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…
- risk 0.53cvss 8.2epss 0.00
Unauthenticated Insecure Direct Object References (IDOR) in Clean Login <= 1.15 versions.
- risk 0.40cvss 6.1epss 0.01
The clean-login plugin before 1.5.1 for WordPress has reflected XSS.
- risk 0.35cvss 5.4epss 0.01
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…
- risk 0.34cvss 5.3epss 0.00
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.
- risk 0.34cvss 5.3epss 0.00
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.
- risk 0.21cvss 4.3epss 0.00
The Clean Login plugin for WordPress is vulnerable to Missing Authorization in versions up to, and including, 1.20.1 due to a missing capability check on the CleanLogin_Shortcode::get_pages_with_shortcodes() function hooked to the save_post action. This makes it possible for…