Log in with Google <= 1.4.2 - Authentication Bypass
Strategic Overview
- Status
- Patched in 1.4.3
- Affected Plugin
- Log in with Google
- Affected Version
<= 1.4.2- CVSS
- 9.8Critical
- Weakness type
- CWE-288 · Authentication Bypass Using an Alternate Path or Channel
- CVE
CVE-2026-28185
At a glance
CVE-2026-28185 is a critical-severity Authentication Bypass Using an Alternate Path or Channel vulnerability in the Log in with Google WordPress plugin, affecting versions <= 1.4.2. It carries a CVSS score of 9.8 (reachable over the network; low attack complexity; high confidentiality, integrity, availability impact). Exploitation requires no authentication. The issue is fixed in version 1.4.3; sites on affected versions should update now. Disclosed August 2026, reported by Abdullah Kareem "cyberkareem".
Vulnerability Overview
The Log in with Google plugin for WordPress is vulnerable to Authentication Bypass in all versions up to, and including, 1.4.2. This makes it possible for unauthenticated attackers to bypass authentication and access other user's accounts, including administrators.
Technical Analysis
The vector marks this flaw as remotely reachable over the network, with low attack complexity — no special timing or configuration is needed, and no privileges on the target site, and no interaction from a victim user. A successful exploit has high impact on confidentiality, integrity, availability — full site compromise territory.
CWE-288: Authentication Bypass Using an Alternate Path or Channel
Reaching this weakness in Log in with Google <= 1.4.2 takes a caller who can reach the endpoint. Authentication bypass through an alternate path means the application has a second route to a protected action that skips the checks the primary route performs.
The protection on the main path becomes irrelevant, because the attacker simply uses the route that never asks. For Log in with Google the fix is 1.4.3: builds <= 1.4.2 are affected, anything from 1.4.3 onward is not.
Remediation
Update to version 1.4.3, or a newer patched version
How does WordSec protect against this?
Because it turns on account access, WordSec's login security is the relevant layer: role-based two-factor, captcha and brute-force limits raise the cost of getting the account this needs. None of that substitutes for the fix: Log in with Google 1.4.3 closes this, and updating the plugin is the step that ends it.
- Login Security
- Alerts
External References
Vulnerability data © Defiant, Inc., provided under the Wordfence Intelligence T&C