dbcve.org
Missing AuthorizationWeakness · CWE-862

CVE-2024-32949

HIGH · 8.3 CVSS v3.1 Published 2026-06-17
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
92/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
Missing Authorization vulnerability in Prince Integrate Google Drive allows Exploiting Incorrectly Configured Access Control Security Levels. This issue affects Integrate Google Drive: from n/a through 1.3.8.

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 · moderate confidence

Missing authorization vulnerability in the Prince Integrate Google Drive plugin (likely a WordPress plugin) allows attackers to bypass or exploit incorrectly configured access control security levels, potentially enabling unauthorized access to Google Drive functionality and data.

MitigationUpdate to the latest version of Prince Integrate Google Drive (beyond 1.3.8) which should contain proper authorization fixes, and review access control configurations to ensure proper permission enforcement.

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
Low
Integrity
Low
Availability
Low

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:L/I:L/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. Locate the plugin installation
    Check your WordPress installation's wp-content/plugins/ directory for a folder named 'prince-integrate-google-drive' or 'prince-integrate-gd'. Alternatively, log into the WordPress admin dashboard and navigate to Plugins > Installed Plugins to search for 'Prince Integrate Google Drive'.
    Affected if The plugin folder or listing is found in your WordPress installation.
  2. Identify the installed version
    In the WordPress admin dashboard, find the plugin in the Installed Plugins list and locate the version number displayed below the plugin name. If accessing the filesystem directly, open the main plugin PHP file (usually prince-integrate-google-drive.php) and look for the version declaration in the plugin header comments.
    Affected if The version number displayed is lower than 1.3.8.
  3. Verify the plugin is active
    In WordPress admin dashboard, go to Plugins > Installed Plugins and check if Prince Integrate Google Drive shows as 'Active' under the plugin status column.
    Affected if The plugin is currently activated.
  4. Inspect user role permissions
    Navigate to WordPress Users > Roles and Capabilities (or use a role editor plugin) to review what capabilities are assigned to each user role, particularly looking for any custom roles or modified capabilities related to Google Drive integration that were not intentionally configured.
    Affected if Unexpected roles or capabilities exist that grant Google Drive access to users who should not have it.
  5. Review Google Drive API access logs
    If the plugin is configured with Google Drive API credentials, access the Google Cloud Console at console.cloud.google.com, navigate to APIs & Services > Dashboard, and review the usage logs and access logs for the Google Drive API to identify any unauthorized or unexpected API calls.
    Affected if API calls originate from unexpected IP addresses, at unusual times, or by users without proper authorization.

Your environment is affected if the Prince Integrate Google Drive plugin is installed, active, and running on a version lower than 1.3.8, or if unauthorized users have gained access to Google Drive functionality through misconfigured permissions.

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.

From vendor data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Update to the latest version of Prince Integrate Google Drive (beyond 1.3.8) which should contain proper authorization fixes, and review access control configurations to ensure proper permission enforcement.

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation5.0 h
  • Testing3.0 h
  • Review / QA2.0 h
12.0 hours of engineering $2,110
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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