CVE-2024-11015

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

Description

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.

Category

9.8
CVSS
Severity: Critical
CVSS 3.1 •
EPSS 0.33%
Affected: tarecord Sign In With Google
Published at:
Updated at:

References

Frequently Asked Questions

What is the severity of CVE-2024-11015?
CVE-2024-11015 has been scored as a critical severity vulnerability.
How to fix CVE-2024-11015?
To fix CVE-2024-11015, make sure you are using an up-to-date version of the affected component(s) by checking the vendor release notes. As for now, there are no other specific guidelines available.
Is CVE-2024-11015 being actively exploited in the wild?
As for now, there are no information to confirm that CVE-2024-11015 is being actively exploited. According to its EPSS score, there is a ~0% probability that this vulnerability will be exploited by malicious actors in the next 30 days.
What software or system is affected by CVE-2024-11015?
CVE-2024-11015 affects tarecord Sign In With Google.
This platform uses data from the NIST NVD, MITRE CVE, MITRE CWE, First.org and CISA KEV but is not endorsed or certified by these entities. CVE is a registred trademark of the MITRE Corporation and the authoritative source of CVE content is MITRE's CVE web site. CWE is a registred trademark of the MITRE Corporation and the authoritative source of CWE content is MITRE's CWE web site.
© 2025 Under My Watch. All Rights Reserved.