Skip to main content
View

Attack ChainAIDerived

Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain

  1. Access
    Register subscriber account on WordPress site
  2. Delivery
    Send crafted AJAX import request
  3. Exploit
    Bypass missing can_import() capability check
  4. Execution
    download_file_to_uploads writes PHP file to uploads
  5. Persist
    Request uploaded web shell
  6. Impact
    Execute arbitrary code as web server

Vulnerability Assessment

Weakness
CWE
OWASP Top 10:2025
A06:2025 - Insecure Design
ASVS 5.0
V5 - File Handling File type validation, storage isolation
MITRE ATT&CK

2 techniques across 2 tactics: Command and Control, Persistence

The technique list with ATT&CK links and the kill-chain view is part of the Basic plan and up.

Exploitation Conditions

Requires one of the four affected WP Cloud Plugins (Use-your-Drive, Out-of-the-Box/Dropbox, Share-one-Drive/OneDrive-SharePoint, or Lets-Box/Box) installed and active at version 2.0 through 3.8.3 on a target WordPress site. Per the CVSS vector (PR:L), the attacker needs at least subscriber-level authentication - realistic on sites with open user registration enabled - and reaches the vulnerable download_file_to_uploads code path through the import AJAX action. The description additionally states the action is hooked via wp_ajax_nopriv_ with no capability check in can_import(), which suggests the write may be reachable without authentication; if confirmed, the subscriber-level prerequisite would not limit exploitation. No user interaction is required (UI:N). Limiting factors: the specific plugin must be installed, and successful RCE depends on the uploads directory permitting PHP execution (many hardened hosts disable PHP in wp-content/uploads, downgrading impact to arbitrary file write/stored content).

Impact

This is a genuine high-priority issue. The CVSS 3.1 vector (AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H = 8.8) describes a network-reachable, low-complexity arbitrary file upload leading to remote code execution, gated only by subscriber-level authentication - a trivially obtainable privilege on any WordPress site allowing open registration. My independent assessment agrees with the vendor 8.8; the only reason it is not 9.8 is the PR:L gate. Notably, the description itself flags a tension worth verifying: it states the import action is 'registered for unauthenticated users via wp_ajax_nopriv_' with 'a missing capability check in can_import()', which would imply PR:N (unauthenticated) exploitation, yet Wordfence's CVSS assigns PR:L (subscriber-and-above). This conflict should be verified with the vendor/Wordfence advisory - if the nopriv path is truly reachable without a valid session, real-world risk is higher than the 8.8 implies. No EPSS score, CISA KEV listing, or public POC was provided in the input, so exploitation is not confirmed as active; however, unauthenticated-or-low-priv RCE in popular WordPress plugins is a class that is routinely mass-scanned and weaponized quickly after disclosure, so the absence of a POC signal should not be read as low urgency. Patch (v3.9.0) availability is indicated by the changelog references.

Exploit ScenarioDerived

An attacker registers a subscriber account (or exploits the wp_ajax_nopriv_ registration path if reachable without auth) on a WordPress site running a vulnerable version of Use-your-Drive, Out-of-the-Box, Share-one-Drive, or Lets-Box, then invokes the import action to call download_file_to_uploads and write a PHP web shell into the uploads directory, bypassing the missing can_import() capability check and the absent mime-type/extension validation. They then request the uploaded file directly to execute arbitrary PHP as the web server, achieving full site compromise. No public exploit code was identified at time of analysis, but the low attack complexity makes reliable exploitation straightforward.

This Week Schedule remediation this week. Why: HIGH severity (CVSS 7.0-8.9).
No patch listed yet 0.6% exploitation probability (EPSS)

Get an e-mail when this CVE is exploited, patched or re-scored. Free account.

Alert me

AnalysisAIv1 – Sep 18, 2026

Arbitrary file upload in WP Cloud Plugins (Use-your-Drive, Out-of-the-Box/Dropbox, Share-one-Drive/OneDrive-SharePoint, and Lets-Box/Box) versions 2.0 through 3.8.3 lets attackers with subscriber-level access write executable files to the WordPress uploads directory, enabling remote code execution (CVSS 8.8). The vulnerable download_file_to_uploads function is reachable through an import AJAX action that is also registered via wp_ajax_nopriv_ and lacks a capability check in can_import(), so the effective authentication prerequisite may be lower than the CVSS PR:L rating suggests, though exploitation still requires one of the four plugins installed and active and depends on the host allowing PHP execution inside wp-content/uploads. No public exploit code identified at time of analysis and the issue is not listed in CISA KEV.

RemediationAI

Vendor-released patch: upgrade each affected plugin - Use-your-Drive, Out-of-the-Box, Share-one-Drive, and Lets-Box - to version 3.9.0 or later, as documented in the vendor changelog at https://documentation.wpcloudplugins.com/other/changelog#id-3.9.0 and https://wpcloudplugins.gitbook.io/docs/other/changelog. If immediate upgrading is not possible, the most effective compensating control is to prevent PHP execution inside wp-content/uploads (for example, an Apache .htaccess rule disabling the PHP handler in that directory, or the equivalent Nginx location block), which converts a successful upload into a harmless arbitrary file write but must be validated against legitimate plugins that rely on executing PHP from uploads; deactivating the four affected plugins entirely removes the vulnerable download_file_to_uploads code path at the cost of losing cloud-storage integration, and restricting or disabling open subscriber registration reduces the pool of users who can reach the import action; a WAF rule that blocks admin-ajax.php requests carrying the plugin's import action can add a layer of protection but risks breaking legitimate import workflows and should be tuned before enforcement. Note that because the import action is registered via wp_ajax_nopriv_, blocking only authenticated requests is insufficient; the mitigation must cover unauthenticated requests as well.

Affected VersionsENISA

Use-your-Drive | Google Drive plugin for WordPress 2.0 ≤3.8.3
WP Cloud Plugins - Box (Lets-Box) 2.0 ≤3.8.3
Share-one-Drive | OneDrive & SharePoint plugin for WordPress 2.0 ≤3.8.3
WP Cloud Plugins - Dropbox (Out-of-the-Box) 2.0 ≤3.8.3

Affected Packages

euvd share_one_drive_onedrive_sharepoint_plugin_for_wordpress no fix
euvd use_your_drive_google_drive_plugin_for_wordpress no fix
euvd wp_cloud_plugins_box_lets_box no fix
euvd wp_cloud_plugins_dropbox_out_of_the_box no fix

Source: OSV (Open Source Vulnerabilities)

Affects your stack

Affects 4 packages in euvd

Checking this CVE against your own stacks and servers is part of the Basic plan and up.

Technical ContextAI · show details

The root cause is CWE-434 (Unrestricted Upload of File with Dangerous Type) in a family of WordPress cloud-storage integration plugins maintained by deleeuw / WP Cloud Plugins. WordPress plugin AJAX handlers are registered through hooks such as wp_ajax_<action> (authenticated users) and wp_ajax_nopriv_<action> (unauthenticated visitors); here the import action is registered for unauthenticated users via wp_ajax_nopriv_, while the can_import() guard performs no capability check. The download_file_to_uploads function then writes the imported file into the uploads directory without first validating the file's extension or contents against get_allowed_mime_types(). Because WordPress permits PHP execution in wp-content/uploads on default or misconfigured servers, the absence of that MIME allow-list check turns an ostensibly benign remote-file import feature into an executable-file drop. The CPE entries confirm four distinct products in the family - Use-your-Drive (Google Drive), Share-one-Drive (OneDrive & SharePoint), Lets-Box (Box), and Out-of-the-Box (Dropbox) - all sharing the same affected code path from version 2.0 through 3.8.3.

Know when Use Your Drive Google Drive Plugin For Wordpress gets its next vulnerability

  • Watch products and get an email when something new is published
  • Check this CVE against your own stack and servers
  • Exploit and PoC references, threat intelligence from 22 sources

No credit card · 7-day full trial

Severity by source

Vendor (Wordfence) PRIMARY 8.8 HIGH
AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
vuln.today AI 8.8 HIGH

Network-reachable low-complexity file upload to RCE with subscriber-level auth per vendor CVSS; full C/I/A from arbitrary code execution, so PR:L and 8.8.

3.1 AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
4.0 AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N

Primary rating from Vendor (Wordfence).

CVSS VectorVendor: Wordfence

Attack Vector
Network
Attack Complexity
Low
Privileges Required
Low
User Interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

DescriptionCVE.org

The WP Cloud Plugins Use-your-Drive, Out-of-the-Box, Share-one-Drive, and Lets-Box plugins for WordPress are vulnerable to Arbitrary File Upload in all versions from 2.0 up to, and including, 3.8.3 via the download_file_to_uploads function. This is due to the import action being registered for unauthenticated users via wp_ajax_nopriv_, a missing capability check in can_import(), and the imported file's extension and contents not being validated against get_allowed_mime_types() before it is written to the uploads directory. This makes it possible for authenticated attackers, with subscriber-level access and above, to upload files that may be executable, which makes remote code execution possible.

Executive ViewAI

Why It Matters

Four widely deployed WordPress file-management plugins (Use-your-Drive, Out-of-the-Box/Dropbox, Share-one-Drive/OneDrive-SharePoint, and Lets-Box/Box) contain a high-severity flaw that allows an attacker to upload and execute code on any affected website, effectively handing over full control of the site and its data. Any organization hosting WordPress with one of these plugins active between versions 2.0 and 3.8.3 is exposed, and because no vendor patch exists today, leadership should treat this as an open risk requiring interim controls rather than waiting for a fix.

Business Impact: High
Compensating Controls

No vendor-released patch identified at time of analysis. Interim mitigations: deactivate or remove the affected plugins where possible; disable PHP execution in wp-content/uploads at the web-server or hosting-platform level; restrict subscriber-level account creation and audit existing low-privilege accounts; deploy WAF rules blocking unauthorized AJAX import requests and PHP files in upload directories; monitor upload directories for unexpected file creation and remove any suspicious PHP files; and maintain tested offline backups for rapid recovery.

Threat Intelligence Overview

EPSS Score
0.6%
Top 53% exploitable
Prevalence
Medium
popular commercial WordPress cloud-storage plugins, tens of thousands of installs, not universal
Data Quality
5 sources
Confidence: Medium

How this decision was reached

The engine reads each signal below and applies a fixed list of rules from top to bottom. The first rule that matches sets the recommended action – like a statement, every line is shown.

SignalValue
Severity HIGH
CISA KEV No
Public POC No
EPSS 0.6%
Patch available No
Active threat No
Deciding rule
HIGH severity (CVSS 7.0-8.9)
What every action level means
Emergency Immediate action required. Criteria: CRITICAL + in CISA KEV (actively exploited) without patch, OR CRITICAL + EPSS > 30% without patch, OR CRITICAL + active threat signals without patch.
Act Now Prioritize within 24-48h. Criteria: in KEV with patch available, OR CRITICAL + public POC, OR HIGH + EPSS > 10%, OR CRITICAL + active threat, OR any CRITICAL severity.
This Week Schedule remediation this week. Criteria: HIGH severity (CVSS 7.0-8.9). Patch within normal change window.
This Month Plan within 30 days. Criteria: MEDIUM severity (CVSS 4.0-6.9), lower exploitation probability. Include in regular patch cycle.
Monitor Track and reassess. Criteria: LOW severity (CVSS 0.1-3.9), minimal exploitation risk. No immediate action needed.

SSVC AssessmentENISA

SSVC Decision
Scheduled
Exploitation
None
System Exposure· derived
Open
Automatable
No
Human Impact
High
Technical Impact
Total

Priority Score

45
Low Medium High Critical
KEV: 0
EPSS: +1
CVSS: +44
PoC: 0
Weaponized: 0
Threat intel: 0
Gov advisory: 0

Attack Technique

Malicious file upload attacks exploit insufficient validation when web applications accept user-provided files.

Remote Code Execution represents the critical moment when an attacker successfully runs arbitrary code on a target system without physical access.

This site uses cookies essential for authentication and security. No tracking or analytics cookies are used. Privacy Policy