dbcve.org
Improper AuthenticationWeakness · CWE-287

CVE-2024-11015

CRITICAL · 9.8 CVSS v3.1 Published 2024-12-12
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable No privileges Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
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.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

The Sign In With Google WordPress plugin fails to validate null values in the authenticate_user function when processing OAuth access tokens and user information. Attackers can exploit this by sending crafted requests with null token data, bypassing authentication entirely and impersonating the first user who configured Google OAuth login (typically the site administrator).

MitigationUpdate the Sign In With Google plugin to version 1.8.1 or later. If immediate update is not possible, deactivate the plugin and use alternative authentication methods.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Locate the Sign In With Google plugin
    Check the WordPress plugins directory at wp-content/plugins/ for a folder named 'sign-in-with-google' or similar Google login plugin. In the plugin's main PHP file, look for a version comment or the 'Version:' field in the plugin header.
    Affected if The plugin folder exists and contains the vulnerable plugin files.
  2. Determine the installed plugin version
    Open the main plugin file (usually sign-in-with-google.php or similar) and locate the version string in the plugin header comment, typically found near the top of the file after 'Version:'.
    Affected if The version is present and is lower than 1.8.1 (e.g., 1.8.0, 1.7.x, etc.).
  3. Verify Google OAuth is configured
    In the WordPress admin dashboard, navigate to the plugin settings page for Sign In With Google. Check if a Google OAuth client ID and client secret are saved and the connection status shows as configured or connected.
    Affected if OAuth credentials are saved and the plugin is actively configured for user logins.
  4. Inspect the authenticate_user function for null validation
    In the plugin PHP files, locate the authenticate_user function. Examine the code that processes OAuth access tokens and user information. Look for conditional checks that validate token data before use.
    Affected if The function lacks proper null/empty validation checks before processing token data, allowing null values to pass through.

Your environment is affected if the Sign In With Google plugin is installed with a version before 1.8.1 AND Google OAuth is actively configured, enabling attackers to send crafted requests with null token data to bypass authentication.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Update the Sign In With Google plugin to version 1.8.1 or later. If immediate update is not possible, deactivate the plugin and use alternative authentication methods.

Recommended fix Moderate confidence

Latest version newer than 1.8.0 from WordPress.org plugin repository

  1. Check the current version of the 'Sign In With Google' plugin installed on your WordPress site
  2. Navigate to Plugins > Installed Plugins in the WordPress admin dashboard
  3. Locate the 'Sign In With Google' plugin and note the current version
  4. Navigate to Plugins > Add New > Upload Plugin or check WordPress.org plugin repository for the latest version
  5. If a version newer than 1.8.0 is available, update the plugin to the latest version
  6. Verify the update was successful and test the Google login functionality
Caveat Review plugin settings after update as configuration may need verification

Generated from the published advisory — verify against the referenced sources before acting.

Have this fixed Scoped from the published advisory
  • Consultation1.0 h
  • Implementation1.0 h
  • Testing2.0 h
  • Review / QA1.0 h
5.0 hours of engineering $860
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,376.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2024-11015 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2024-11015 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data