CVE-2026-90977 Clean Login CVE debrief

Who should care

Defenders responsible for WordPress installations using the Clean Login plugin should assess exposure and verify the presence of version 1.19 or later. They should also ensure that CAPTCHA verification is properly enforced on the registration form to prevent unauthorized account creation.

Why it matters

The Clean Login WordPress plugin vulnerability allows unauthenticated users to bypass CAPTCHA verification and create accounts without solving it, potentially leading to unauthorized access and automated attacks. Defenders should prioritize verifying the presence of version 1.19 or later and ensure proper CAPTCHA enforcement.

• Defenders should verify the presence of Clean Login WordPress plugin version 1.19 or later to prevent unauthorized account creation
• Defenders should ensure that CAPTCHA verification is properly enforced on the registration form to prevent automated attacks
• Defenders should monitor registration form activity for suspicious behavior to detect potential attacks

Technical summary

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. The vulnerability has a CVSS score of 5.3 and a severity of MEDIUM. This issue affects WordPress installations using the Clean Login plugin, and defenders should prioritize verifying the presence of version 1.19 or later and ensure proper CAPTCHA enforcement. The CVE record and NVD entry provide details on the vulnerability, including its CVSS score and vector.

Defensive priority

Defenders should prioritize verifying the presence of the Clean Login WordPress plugin version 1.19 or later, and ensure that CAPTCHA verification is properly enforced on the registration form.

Recommended defensive actions

• Verify the presence of Clean Login WordPress plugin version 1.19 or later
• Ensure CAPTCHA verification is properly enforced on the registration form
• Monitor registration form activity for suspicious behavior
• Review compensating controls for exposed systems while remediation is scheduled and verified
• Check relevant monitoring, detection, and logs for exposed assets that need extra review
• Track exceptions, retest remediated assets, and close the item only after evidence is documented
• Confirm whether affected product deployments exist in managed environments and assign an owner for follow-up

Evidence notes

The CVE record and NVD entry provide details on the vulnerability, including its CVSS score and vector. WPScan vulnerability entry explicitly identifies the Clean Login WordPress plugin before 1.19 as the affected component.

Sources and references

Methodology and review provenance

AI-assisted synthesis based on stored public vulnerability evidence. System validation, approval state, and publication status do not by themselves establish human review of this revision. PatchSiren helps prioritize defensive review and does not prove exposure or remediation on any system.