Clean Login
clean-login · plugin
Known security vulnerabilities for Clean Login. Find out in seconds which version runs on your site with WP Lens.
4 known vulnerabilities
3 exploitable without logging in · 1 with public exploit code · latest Jun 17, 2026
Listed on wordpress.org · latest 1.20 · last updated Oct 1, 2026 · 5K+ installs
wordpress.org status checked on Oct 2, 2026
Vulnerabilities
- High 8.8
CVE-2024-8252contributor+≤ 1.14.5
Clean Login <= 1.14.5 - Authenticated (Contributor+) Local File Inclusion
- High 8.2
CVE-2026-54184unauthenticated≤ 1.15
WordPress Clean Login plugin <= 1.15 - Insecure Direct Object References (IDOR) vulnerability
- Medium 6.5
CVE-2017-8875unauthenticated · needs a click
CSRF in the Clean Login plugin before 1.8 for WordPress allows remote attackers to change the login redirect URL or logout redirect URL.
- Medium 6.1
CVE-2015-9336unauthenticated · needs a click
The clean-login plugin before 1.5.1 for WordPress has reflected XSS.
The access label is read from the record's own text (e.g. “subscriber+”: subscriber and above). When the text names no role, CVSS decides between “login required” and “high privilege”; no role name is invented. “Needs a click”: the attack depends on a logged-in user following a link (CSRF, reflected XSS).