WordPress security by component
Clean Login
Plugin description
Clean Login is a WordPress component with 5 published CVE records in this archive. The latest tracked vulnerability was published Jun 17, 2026; the highest CVE/CNA score is 8.8.
Plugin slug:
clean-loginLatest vulnerability
CVE-2026-54184: Clean Login: A security weakness
Clean Login is affected by a security weakness. The vulnerable path is reachable without authentication. The resulting impact depends on how the affected component exposes the vulnerable operation. The published affected range is n/a through 1.15.
| Safe version |
|
||
|---|---|---|---|
| Jun 17, 2026 |
CVE-2026-54184
Clean Login: A security weakness
Clean Login is affected by a security weakness. The vulnerable path is reachable without authentication. The resulting impact depends on how the affected component exposes the vulnerable operation. The published affected range is n/a through 1.15.
|
1.16 |
CVE8.2
NVDPending
|
| Aug 30, 2024 |
CVE-2024-8252
Clean Login: Filesystem traversal
Clean Login is affected by filesystem traversal. Exploitation requires at least contributor-level access. A crafted path can escape the intended directory and reach files or directories elsewhere on the server.
|
See mitigation notes |
CVE8.8
NVD8.8
|
| Feb 06, 2023 |
CVE-2022-4838
Clean Login: Cross-site scripting
Clean Login is affected by cross-site scripting. Exposure depends on how the affected operation is made reachable by the site. Injected script can execute in the affected site's origin when the vulnerable output is viewed.
|
See mitigation notes |
CVE5.4
NVD5.4
|
| Aug 22, 2019 |
CVE-2015-9336
Clean Login: Cross-site scripting
Clean Login is affected by cross-site scripting. Exposure depends on how the affected operation is made reachable by the site. Injected script can execute in the affected site's origin when the vulnerable output is viewed.
|
See mitigation notes |
CVE6.1
NVD6.1
|
| May 10, 2017 |
CVE-2017-8875
Clean Login: Cross-site request forgery
Clean Login is affected by cross-site request forgery. Exposure depends on how the affected operation is made reachable by the site. Exploitation relies on a signed-in privileged user submitting an attacker-controlled request.
|
See mitigation notes |
CVE6.5
NVD6.5
|