Sign In With Google <= 1.8.0 — Authentication Bypass in authenticate_user

Am I affected?

• Check your version: in wp-admin go to Plugins → Installed Plugins and read the version under Sign In With Google.
• No admin access? Run a passive check of your site. It reads public files only.
• No account is needed to exploit this. Treat any exposed site on an affected version as at risk.

What to do

1. No known patch available. Please review the vulnerability's details in depth and employ mitigations based on your organization's risk tolerance. It may be best to uninstall the affected software and find a replacement.
2. Rotate administrator passwords and application secrets if the site ran a vulnerable version while publicly reachable.
3. Watch Sign In With Google to get an email when the next vulnerability is published.

Advisory

Source description from Wordfence Intelligence, credited to shaman0x01.

The Sign In With Google plugin for WordPress is vulnerable to authentication bypass in all versions up to, and including, 1.8.0. This is due to the 'authenticate_user' user function not implementing sufficient null value checks when setting the access token and user information. This makes it possible for unauthenticated attackers to log in as the first user who has signed in using Google OAuth, which could be the site administrator.

Exploits & references

Proof-of-concept & detection

No public proof-of-concept or detection template is known for this vulnerability.

Advisories & patches

• Advisorywordfence.com

Timeline

1. Dec 11, 2024

   CVE published

   Severity critical, CVSS 9.8

2. Nov 13, 2026

   Record last updated