dbcve.org
Missing AuthorizationWeakness · CWE-862

CVE-2024-2086

CRITICAL · 10.0 CVSS v3.1 Published 2024-03-30
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 Integrate Google Drive – Browse, Upload, Download, Embed, Play, Share, Gallery, and Manage Your Google Drive Files Into Your WordPress Site plugin for WordPress is vulnerable to unauthorized access of data, modification of data, and loss of data due to a missing capability check on multiple AJAX in all versions up to, and including, 1.3.8. This makes it possible for authenticated attackers to modify plugin settings as well as allowing full read/write/delete access to the Google Drive associated with the plugin.

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 WordPress plugin 'Integrate Google Drive' versions up to 1.3.8 lacks capability checks on multiple AJAX endpoints, allowing any authenticated user (regardless of role/privileges) to execute these functions. This enables attackers to modify plugin settings and perform full read/write/delete operations on the connected Google Drive account.

MitigationUpdate the plugin to version 1.3.9 or later which implements proper capability checks. Until patched, disable user registration and monitor for unauthorized AJAX requests.

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
Changed
Confidentiality
High
Integrity
High
Availability
Low

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

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. Verify Integrate Google Drive plugin is installed
    Navigate to WordPress admin dashboard > Plugins and search for 'Integrate Google Drive' or check the plugin directory for the plugin folder
    Affected if The plugin is installed and active in WordPress
  2. Identify installed plugin version
    In WordPress admin > Plugins > Installed Plugins, locate 'Integrate Google Drive' and note the version number displayed
    Affected if Version is 1.3.8 or lower (the vulnerable versions)
  3. Check WordPress user registration settings
    Go to WordPress admin > Settings > General and look for the 'Membership' setting 'Anyone can register' - verify whether it is enabled
    Affected if User registration is open (checked), allowing any user to register and exploit the AJAX vulnerability
  4. Inspect AJAX endpoint accessibility
    Use a tool like curl or browser dev tools to test a sample AJAX request to wp-admin/admin-ajax.php with a low-privilege or newly registered user account
    Affected if AJAX requests execute successfully without proper capability verification (requires manual testing with a non-admin account)

A WordPress site is affected if the Integrate Google Drive plugin versions 1.3.8 or below are installed, especially with user registration enabled, as any authenticated user can exploit the AJAX endpoint vulnerability.

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 plugin to version 1.3.9 or later which implements proper capability checks. Until patched, disable user registration and monitor for unauthorized AJAX requests.

Recommended fix Moderate confidence

1.3.9 or later

  1. 1. Back up your WordPress site and database before making any changes
  2. 2. Navigate to Plugins > Installed Plugins in the WordPress admin dashboard
  3. 3. Locate the 'Integrate Google Drive' plugin
  4. 4. Check if an update to version 1.3.9 or later is available
  5. 5. If available, update the plugin to the latest version
  6. 6. Verify the update was successful and test Google Drive integration functionality

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

Have this fixed Scoped from the published advisory
  • Consultation3.0 h
  • Implementation2.0 h
  • Testing4.0 h
  • Review / QA2.0 h
11.0 hours of engineering $1,920
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2024-2086 — 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-2086 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