dbcve.org
Information ExposureWeakness · CWE-200

CVE-2025-12139

HIGH · 7.5 CVSS v3.1 Published 2025-11-05
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
84/100
Remediation priority · High
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 File Manager for Google Drive – Integrate Google Drive with WordPress plugin for WordPress is vulnerable to sensitive information exposure in all versions up to, and including, 1.5.3 via the "get_localize_data" function. This makes it possible for unauthenticated attackers to extract sensitive data including Google OAuth credentials (client_id and client_secret) and Google account email addresses.

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 File Manager for Google Drive WordPress plugin versions up to 1.5.3 contain a sensitive information disclosure vulnerability in the 'get_localize_data' function. This function, accessible to unauthenticated users, exposes Google OAuth credentials (client_id and client_secret) and Google account email addresses through improper data handling.

MitigationUpdate the plugin to the latest version immediately. Rotate all exposed OAuth credentials (client_id and client_secret) as a precaution since they may have been compromised by unauthenticated attackers. Implement proper authentication/authorization checks on the vulnerable function.

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
None
Availability
None

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

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 the File Manager for Google Drive plugin is installed
    Check the WordPress plugins directory at wp-content/plugins/ for a folder named 'file-manager-for-google-drive' or similar. Also check via WP admin under Plugins > Installed Plugins.
    Affected if The plugin folder exists in the WordPress installation
  2. Determine the installed plugin version
    Open the main plugin PHP file (usually file-manager-for-google-drive.php) and look for the 'Version' header comment in the file header. Alternatively, check the plugin row in WordPress admin plugins list.
    Affected if The version number is 1.5.3 or lower (any version up to and including 1.5.3)
  3. Confirm the plugin is active
    Check WordPress admin under Plugins > Installed Plugins to see if the plugin is activated, or query the wp_options table for the active_plugins option.
    Affected if The plugin is currently activated on the WordPress site
  4. Check for exposed Google OAuth credentials
    Inspect the plugin settings page in WordPress admin (usually under Settings or a dedicated menu item for this plugin). Look for fields labeled 'Client ID', 'Client Secret', or 'Email' that may be visible or stored in plain text.
    Affected if Google OAuth client_id and client_secret values or Google account email addresses are stored in the plugin configuration and readable by unauthenticated users
  5. Test unauthenticated access to the vulnerable function
    Send a GET or POST request to the site endpoint that calls the get_localize_data function (commonly via wp-admin/admin-ajax.php?action=get_localize_data or similar AJAX endpoint). Check the response for JSON data containing 'client_id', 'client_secret', or email addresses.
    Affected if The response returns Google OAuth credentials or email addresses without requiring authentication

If the File Manager for Google Drive plugin version 1.5.3 or lower is installed and active, and the get_localize_data function is accessible without authentication exposing OAuth credentials or email addresses, the environment is affected by CVE-2025-12139.

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 the latest version immediately. Rotate all exposed OAuth credentials (client_id and client_secret) as a precaution since they may have been compromised by unauthenticated attackers. Implement proper authentication/authorization checks on the vulnerable function.

Recommended fix High confidence

Version 1.5.4 or later

  1. 1. Log in to the WordPress admin dashboard
  2. 2. Navigate to Plugins > Installed Plugins
  3. 3. Locate 'File Manager for Google Drive' in the plugin list
  4. 4. Click 'Update now' if an update is available, or manually upload version 1.5.4 or later of the plugin
  5. 5. Verify the update was successful and the plugin is functioning correctly

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

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation3.0 h
  • Testing2.0 h
  • Review / QA1.0 h
8.0 hours of engineering $1,420
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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