Sign In With Google
Approved changes feed: RSS · Atom
cpe:2.3:a:tarecord:sign_in_with_google:*:*:*:*:*:*:*:*part: a version: * update: *
| Vendor | Tarecord (565971ef-eda2-5e91-a789-6584cb7139a6) |
|---|---|
| Product | Sign In With Google (bb6e5284-b46e-5e2b-b130-5343a63a8d3c) |
| Edition | * |
| Language | * |
| Software edition | * |
| Target software | * |
| Target hardware | * |
| Other | * |
Notes
Imported from gcve-enriched-dumps CVE data
PURL mappings
| PURL | Source | Last updated |
|---|---|---|
| No PURL mappings for this CPE yet. | ||
Vulnerability references
| Identifier | cpeApplicability | Submitted | db.gcve.eu details | Rationale |
|---|---|---|---|---|
CVE:CVE-2024-11015 |
vulnerable | 2026-06-08 06:23:48.429071 |
Sign In With Google <= 1.8.0 - Authentication Bypass in authenticate_user
CRITICAL (9.8)
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.
Published: 2024-12-12T03:23:08.908Z
Updated: 2026-04-08T17:15:43.111Z |
Imported from gcve-enriched-dumps CVE data |
Contribute
You can submit an edit proposal for this CPE entry or suggest a related product/vendor addition using the action button above.
Inspect record JSON
Open this panel to browse, search, copy or download the JSON record.