Summary
CVE-2026-77002 is a critical authentication bypass vulnerability (CWE-287: Improper Authentication) affecting the SmilePass Selfie Login WordPress plugin, versions through 1.0.2. The plugin’s selfie-based login mechanism performs no server-side verification of the identity it is asked to authenticate, allowing a completely unauthenticated attacker to log in as any registered account on the site, including administrators. The flaw carries a CVSS v3.1 base score of 9.8 (Critical).
Technical details
- Root cause: The plugin’s facial-recognition login flow trusts the identity claim submitted by the client without performing genuine server-side verification that the presented "selfie" match corresponds to the account being authenticated as.
- Trigger conditions: No prior authentication, special privileges, or user interaction from a victim is required — an attacker only needs network access to the WordPress login endpoint exposing the SmilePass login functionality.
- Attack vector: Network (remote, unauthenticated). Attack complexity is low and no privileges or user interaction are required (AV:N/AC:L/PR:N/UI:N).
- Impact: Full compromise of confidentiality, integrity, and availability — an attacker can impersonate any registered user, including site administrators, resulting in complete site takeover.
Affected software
- SmilePass Selfie Login WordPress plugin — all versions through 1.0.2 (0 ≤ version ≤ 1.0.2)
Severity
- CVSS v3.1 Base Score: 9.8 (Critical)
- Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
Mitigation and recommended actions
- Immediate: No patched version of SmilePass Selfie Login has been published to address this issue as of the time of this report. Security teams should treat this plugin as unsafe to run in its current form.
- If no patch is available:
- Deactivate and remove the SmilePass Selfie Login plugin from all WordPress installations until an official fix is released by the vendor.
- Audit user accounts and administrator logins for unexpected or unauthorized access that may indicate prior exploitation.
- Enforce strong, unique passwords and enable additional authentication factors (e.g., 2FA via a trusted plugin) as compensating controls for administrator and privileged accounts.
- Restrict or firewall access to WordPress login and plugin-specific authentication endpoints where feasible while remediation is pending.
- Monitor site logs for unusual login activity, new administrator account creation, or unexpected plugin/theme changes.

