Plugins · clean-login · data as of 2026-11-04
Is Clean Login safe? Known vulnerabilities and latest version
- Latest version
- 2.0.1
- Last updated
- 2026-10-30
- Active installs
- 5,000+
- Known issues on record
- 8
- Unpatched in latest
- 0
- Tested up to WP
- 7.1.4
Frontend login, registration, profile and password reset forms with blocks or shortcodes. WPML certified, reCAPTCHA and WooCommerce compatible. — by Alberto Hornero
What to do
- Update to the latest version (2.0.1). Anything older than 1.21 has at least one known issue listed below. Dashboard → Updates, or Plugins → “update now”.
- If you cannot update right away, deactivate it until you can.
- Turn on auto-updates for it: Plugins → “Enable auto-updates” on its row.
- If you ran a vulnerable version and something looks off (spam pages, strange admins, redirects), run the free scan.
With WP-CLI: wp plugin get clean-login --field=version shows what you run; wp plugin update clean-login updates it.
Check your version
Known vulnerabilities
8 on record, newest first. “Affected” is the version range the source gives; “fixed in” is the version the source names, or (marked *) the first wordpress.org release after the last affected version.
medium 4.3 CVE-2026-116610 · published 2026-10-28
Missing authorization check in Clean Login (1.20.1 and older)
- Affected
- 1.20.1 and older
- Fixed in
- 1.21 *
- Access needed (per CVSS)
- Needs a low-level account (e.g. subscriber)
- Range from
- CVE record (the advisory publisher) · score by Wordfence
Details from the advisory
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 authenticated attackers, with Contributor-level access and above, to overwrite the plugin's cl_login_url/cl_login_id/cl_register_url/cl_register_id/cl_restore_url/cl_restore_id/cl_edit_url/cl_edit_id/cl_change_password_url/cl_change_password_id options with the ID and permalink of a post they themselves authored — simply by embedding the plugin's shortcodes in their own post content.
NVD CVE-2026-116610Wordfence advisoryCode change (fix)Plugin source
medium 5.3 CVE-2026-90976 · published 2026-09-18
Missing authorization check in Clean Login (older than 1.19)
- Affected
- older than 1.19
- Fixed in
- 1.19
- Access needed (per CVSS)
- No login needed
- Range from
- CVE record (the advisory publisher) · score by WPScan
Details from the advisory
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.
medium 5.3 CVE-2026-90977 · published 2026-09-18
Security issue in Clean Login (older than 1.19)
- Affected
- older than 1.19
- Fixed in
- 1.19
- Access needed (per CVSS)
- No login needed
- Range from
- CVE record (the advisory publisher) · score by WPScan
Details from the advisory
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.
high 8.2 CVE-2026-54184 · published 2026-06-17
Missing authorization check in Clean Login (1.15 and older)
- Affected
- 1.15 and older
- Fixed in
- 1.16
- Access needed (per CVSS)
- No login needed
- Range from
- CVE record (the advisory publisher) · score by Patchstack
Details from the advisory
Unauthenticated Insecure Direct Object References (IDOR) in Clean Login <= 1.15 versions.
high 8.8 CVE-2024-8252 · published 2024-08-30
File inclusion in Clean Login (1.14.5 and older)
- Affected
- 1.14.5 and older
- Fixed in
- 1.14.6 *
- Access needed (per CVSS)
- Needs a low-level account (e.g. subscriber)
- Range from
- CVE record (the advisory publisher) · score by NVD
Details from the advisory
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.
NVD CVE-2024-8252Wordfence advisoryCode change (fix)Plugin source
medium 5.4 CVE-2022-4838 · published 2023-02-06
Stored cross-site scripting (XSS) in Clean Login (older than 1.13.7)
- Affected
- older than 1.13.7
- Fixed in
- 1.13.7
- Access needed (per CVSS)
- Needs a low-level account (e.g. subscriber); someone on the site has to click a link or open a page
- Range from
- CVE record (the advisory publisher) · score by NVD
Details from the advisory
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.
medium 6.1 CVE-2015-9336 · published 2019-08-22
Reflected cross-site scripting (XSS) in Clean Login (older than 1.5.1)
- Affected
- older than 1.5.1
- Fixed in
- 1.5.1
- Access needed (per CVSS)
- No login needed; someone on the site has to click a link or open a page
- Range from
- NVD analysis · score by NVD
Details from the advisory
The clean-login plugin before 1.5.1 for WordPress has reflected XSS.
medium 6.5 CVE-2017-8875 · published 2017-05-10
Cross-site request forgery (CSRF) in Clean Login (1.7.12 only)
- Affected
- 1.7.12 only
- Fixed in
- 1.10 *
- Access needed (per CVSS)
- No login needed; someone on the site has to click a link or open a page
- Range from
- NVD analysis · score by NVD
Details from the advisory
CSRF in the Clean Login plugin before 1.8 for WordPress allows remote attackers to change the login redirect URL or logout redirect URL.
Recent activity
- 2026-10-30 — latest release on wordpress.org (2.0.1).
- 2026-10-28 — Missing authorization check disclosed (CVE-2026-116610), fixed in 1.21.
- 2026-09-18 — Missing authorization check disclosed (CVE-2026-90976), fixed in 1.19.
- 2026-09-18 — Security issue disclosed (CVE-2026-90977), fixed in 1.19.
Get an email when Clean Login has a new vulnerability
Free. We check the CVE feeds every day and email you only when a new issue for Clean Login (clean-login) is published or a fix ships. Unsubscribe in one click.
Browse vulnerabilities
Types found in this plugin: Missing authorization (3) · Cross-site scripting (XSS) (2) · File inclusion (1) · Cross-site request forgery (CSRF) (1)
Where this data comes from
- Version, last update, installs: wordpress.org/plugins/clean-login (Plugins API), fetched 2026-11-04.
- Vulnerabilities: NIST National Vulnerability Database (NVD), checked 2026-11-04. This product uses data from the NVD API but is not endorsed or certified by the NVD.
- Each record links to its CVE page and to the original advisory (Wordfence, Patchstack or WPScan) where there is one. We only list a CVE here when its references or its advisory name this exact plugin, so a few real issues may be missing; none should be about a different plugin. Spot an error? Email Daniel.
Badge for your site or docs (states facts with a date, not a verdict):
<a href="https://laskyr.com/plugins/clean-login"><img src="https://laskyr.com/plugins/clean-login/badge.svg" alt="Clean Login vulnerability status"></a>