fluentwiz · Cloud Storage Manager for Fluent Forms – Google Drive, Dropbox, OneDrive, S3 Uploads · CWE-22 · published 2026-11-14
CVE-2026-120522Cloud Storage Manager for Fluent Forms <= 1.2.0 - Unauthenticated Arbitrary File Write via Google Drive Filename Path Traversal
Routine No exploitation evidence; EPSS 0.8%.
CVE-2026-120522 is not known to be exploited in the wild. EPSS estimates a 0.8% chance of exploitation in the next 30 days, higher than 57% of all CVEs. This Cloud Storage Manager for Fluent Forms – Google Drive, Dropbox, OneDrive, S3 Uploads vulnerability: CVSS 9.8 (v3.1), attacks can be automated, a successful attack gives total control of the component. Routine: patch when convenient.
Jump to: Remediation Exploit intelAffected versionsDescription
Remediation#
No fixed version is recorded here yet. Check the vendor advisory linked from the CVE record below.
Exploit intelligence#
| Signal | Value | Source |
|---|---|---|
| Known exploited | No | CISA KEV |
| Ransomware use | — | CISA KEV |
| EPSS (30-day exploitation probability) | 0.8% (57th pct) | FIRST EPSS v2026.06.15 |
| CVSS base score | 9.8 (v3.1)CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H | CNA / CISA ADP |
| SSVC exploitation | none | CISA Vulnrichment |
| SSVC automatable | Yes | CISA Vulnrichment |
| SSVC technical impact | total | CISA Vulnrichment |
Weakness: CWE-22: Improper Limitation of a Pathname to a Restricted Directory
Affected versions (from the CVE record)#
- fluentwiz Cloud Storage Manager for Fluent Forms – Google Drive, Dropbox, OneDrive, S3 Uploads
0through1.2.0(affected)
Description (from the CVE record)#
The Cloud Storage Manager for Fluent Forms – Google Drive, Dropbox, OneDrive, S3 Uploads plugin for WordPress is vulnerable to Arbitrary File Write in all versions up to, and including, 1.2.0. This is due to missing authorization checks on the `connection/{driver}/save` and `/download/single-file` REST endpoints, combined with insufficient path validation in the Google Drive `downloadFile()` function, where the Google Drive metadata `name` value is concatenated into a local path without `basename()`, `sanitize_file_name()`, or canonical path validation. This makes it possible for unauthenticated attackers to store attacker-controlled Google Drive credentials, trigger a download of an attacker-owned file whose provider-returned filename contains path traversal, and write attacker-controlled content outside the intended `downloads` directory. When the written file has a PHP extension and lands in a web-accessible location, this can lead to remote code execution.
Quoted from the CVE Program record.