Auth bypass in Tarecord Sign In With Google
CVE-2024-11015
- CVSS v3
- 9.8 Critical
- Public exploits
- None known
- EPSS
- 0.008 · 57.7th percentile
- Published
- 2024-12-12
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.
Vulnerability class: Broken Authentication
Published · last modified .
CVSS v3 metric
CVSS v3 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.
- Attack Vector
- Network
AV:N - Attack Complexity
- Low
AC:L - Privileges Required
- None
PR:N - User Interaction
- None
UI:N - Scope
- Unchanged
S:U - Confidentiality
- High
C:H - Integrity
- High
I:H - Availability
- High
A:H
EPSS exploit prediction
EPSS 0.008, 57.7th percentile (last changed ); unchanged over 30 days. About EPSS.
Affected products
- Tarecord Sign In With Google — versions 0
Weakness classification (CWE)
Public exploits and proof-of-concept code
Also mentioned in 2 other repositories (20142995/nuclei-templates, cyb3r-w0lf/nuclei-template-collection). These reference the CVE in a list, notes or a scanner and are not exploit code for it.