CVE-2024-2086

Integrate Google Drive <= 1.3.8 - Missing Authorization to Unauthenticated Settings Modification and Export

2024-03-29 00:00
Krzysztof Zając

Strategic Overview

Status
Patched in 1.3.9
Affected Version
<= 1.3.8
CVSS
10.0Critical
Weakness type
CWE-862 · Missing Authorization
CVE
CVE-2024-2086
View all File Manager for Google Drive – Integrate Google Drive vulnerabilities

At a glance

CVE-2024-2086 is a critical-severity Missing Authorization vulnerability in the File Manager for Google Drive WordPress plugin, affecting versions <= 1.3.8. It carries a CVSS score of 10.0 (reachable over the network; low attack complexity; high confidentiality, integrity impact). Exploitation requires no authentication. The issue is fixed in version 1.3.9; sites on affected versions should update now. Disclosed March 2024, reported by Krzysztof Zając.

Vulnerability Overview

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 Analysis

The vector marks this flaw as remotely reachable over the network, with low attack complexity — no special timing or configuration is needed, and no privileges on the target site, and no interaction from a victim user. A successful exploit has high impact on confidentiality, integrity.

CWE-862: Missing Authorization

Reaching this weakness in File Manager for Google Drive <= 1.3.8 takes no account at all. A missing authorization check means a function is reachable by anyone who can reach the endpoint, because the code never asks whether the caller is allowed to perform the action.

Any user who can reach the endpoint gets to run an action reserved for higher-privileged roles, from reading protected data to changing settings or content. For File Manager for Google Drive the fix is 1.3.9: builds <= 1.3.8 are affected, anything from 1.3.9 onward is not.

Remediation

Update to version 1.3.9, or a newer patched version

How does WordSec protect against this?

This one needs no account at all, which puts it outside what login hardening can reach; WordSec's login security narrows the account-level paths around it, and the firewall is what inspects the request itself. None of that substitutes for the fix: File Manager for Google Drive 1.3.9 closes this, and updating the plugin is the step that ends it.

  • Login Security
  • Alerts

External References

Related records

Vulnerability data © Defiant, Inc., provided under the Wordfence Intelligence T&C