Log in with Google · Security record
Is Log in with Google safe?
No known vulnerability affects the current version (1.4.5). 1 issue was found in earlier versions and fixed, the latest disclosed on Aug 13, 2026.
Checked 5 days ago against the WPVulnerability database, for version 1.4.5.
How it’s looked after
- Last release
- Nov 6, 2026 (2 days ago)
- Releases in the last year
- 4
- Tested up to
- WordPress 7.0.8
- Support resolved
- 0 of 1 threads in two months
- Active installs
- 6K+
1 known vulnerability
- 1 critical
None affects the current version.
Every known vulnerability in Log in with Google
Newest first, with any that affect the current version at the top.
- critical
Authentication Bypass
Fixed in 1.4.3 · CVE-2026-28185 · Aug 13, 2026 · Wordfence
Questions about Log in with Google’s security
Is Log in with Google safe to use?
No known vulnerability affects its current version. Earlier versions had issues that are now fixed, so keep Log in with Google updated: most attacks target sites that haven’t updated.
Does Log in with Google have known security vulnerabilities?
None that affect the current version. WPVulnerability’s database lists 1 older issue, fixed in earlier versions, so keep Log in with Google up to date.
Is Log in with Google still maintained?
Yes. Its last release was 2 days ago. Its authors resolved 0 of the 1 support threads opened in the last two months.
Is Log in with Google compatible with the latest WordPress?
It’s tested up to WordPress 7.0.8, one version behind the current 7.1. Authors often update this line a few weeks after a release.
Hear about the next one first
Track your plugin on TrackWP and get an alert when a new vulnerability affecting it is published. Every plan has it, the free Starter too; Boost and FullCharge email it at once.
Start freeVulnerability data from WPVulnerability (CC0), which gathers records from CVE, Wordfence, Patchstack and WPScan. A clean record isn’t a guarantee: keep every plugin updated.