On this page (7 sections)

A critical vulnerability, CVE-2026-120522, affects the Cloud Storage Manager for Fluent Forms plugin for WordPress (Google Drive, Dropbox, OneDrive, S3 Uploads). According to the GitHub Advisory Database entry, all versions up to and including 1.2.0 let unauthenticated attackers write files to the server, which can lead to remote code execution.

If you run WordPress with this plugin installed, treat it as urgent. The advisory lists a CVSS score of 9.8, and no login is needed to reach the vulnerable code.

What happened

The vulnerability was published on November 14, 2026 through the National Vulnerability Database and the GitHub Advisory Database. The GitHub entry is marked unreviewed and does not list a package, affected range or patched version in its structured fields, so the version information comes from the description text only.

A Wordfence threat intelligence entry and a WordPress plugin repository changeset are referenced by the advisory. We have not been able to confirm from the research what the changeset contains, so check it yourself before assuming it is a complete fix. Note also that the NVD record repeats the GitHub text and is not independent confirmation, and coverage so far is thin.

How the flaw works

Two problems combine here. The first is missing authorization: the plugin's connection/{driver}/save and /download/single-file REST endpoints do not check who is calling them. The second is path traversal (CWE-22) in the Google Drive downloadFile() function. It takes the file name returned by Google Drive and appends it to a local path without basename(), sanitize_file_name() or canonical path validation.

In plain terms, the advisory says an attacker can store their own Google Drive credentials in the plugin, make the site download a file from their own Drive, and choose a file name containing directory traversal sequences. The file then lands outside the intended downloads directory with attacker-controlled content. If that file has a PHP extension and ends up somewhere the web server can serve and execute, the attacker gets remote code execution.

The code execution step depends on the written file having a PHP extension and landing in a web-accessible location. The advisory describes this as a condition, so not every site will be equally exposed, but you should not rely on server layout alone.

Who is affected

  • Sites with the Cloud Storage Manager for Fluent Forms plugin active at version 1.2.0 or earlier.
  • Sites where the plugin is installed but deactivated may still be worth removing; the research does not say whether inactive plugins are reachable, so do not assume they are safe.
  • Agencies and hosts managing many WordPress sites, where this plugin may have been added to a form setup without much attention.

The attack needs no account and no user interaction, and it works over the network. That makes automated scanning of public sites realistic, although the research reports no exploitation so far.

How to check your exposure

First find out whether the plugin is installed and which version. This WP-CLI command, run from your WordPress root, lists installed plugins with their status and version; look for the Cloud Storage Manager entry and compare its version with 1.2.0.

List installed plugins with status and version (run in the WordPress root)WP-CLI
wp plugin list --fields=name,status,version

You can also check Plugins in the WordPress admin, or compare against known vulnerabilities per plugin and our guide on whether your plugin is vulnerable.

Next, look for signs of abuse. This grep, run on the server against your web server access log (adjust the path for your setup), shows requests to the two endpoints named in the advisory. Hits from unfamiliar addresses deserve a closer look.

Search an access log for requests to the affected REST endpoints (adjust the log path)Shell
grep -E "connection/.+/save|download/single-file" /var/log/nginx/access.log

What to do now

  1. Identify every site where the Cloud Storage Manager for Fluent Forms plugin is installed and note its version.
  2. Check the plugin's page in the WordPress repository for an update newer than 1.2.0 and apply it if one exists. The advisory does not name a fixed version, so confirm the version you install is newer than 1.2.0.
  3. If no fixed release is available, deactivate and delete the plugin until one is, and move file uploads to another method in the meantime.
  4. Search the site for PHP files that should not exist, especially in upload, download and plugin directories, and compare against a clean copy of your plugins and core.
  5. Review access logs for the two endpoints above and for new or unexpected PHP files requested directly.
  6. If you find anything suspicious, follow the steps in website hacked: what to do, and rotate WordPress admin passwords, database credentials and any cloud storage keys connected to the site.
  7. Restrict PHP execution in directories meant to hold only downloads or uploads, using your web server configuration.
Caution. Deleting a plugin removes its settings and can break forms that depend on it. Take a full backup first and test on staging if the forms are business critical.

Detection and monitoring

Because the flaw ends in file creation, unexpected changes on disk are the clearest signal. File integrity monitoring on the WordPress directory, alerts on new PHP files in upload paths, and regular log review all help. A web application firewall can add a layer by filtering suspicious requests to REST routes; read what a WAF is for what it can and cannot do, and remember it is not a substitute for updating.

For an outside view, you can run the free malware scanner on your site, which looks at what is visible from the web. Its limits are explained in what outside-in malware detection can and cannot see, so a clean result does not rule out a hidden file.

What is still unknown

  • The advisory does not list a patched version.
  • Whether the changeset linked from the advisory is the full fix has not been verified here.
  • No exploitation in the wild is reported in the research, and the CVE is not in CISA KEV as of November 14, 2026.
  • Only the GitHub advisory and its NVD copy are in our sources, so details may change as the vendor or other researchers publish more.

We will update this article if a fixed version or exploitation reports appear.

Sources

This article is based on the public sources below. Details can change as vendors and researchers publish more; check the original advisories before acting on version numbers.

  1. CVE-2026-120522 - GitHub Advisory Databasegithub.com
  2. CVE-2026-120522: The Cloud Storage Manager for Fluent Forms – Google Drive, Dropbox, OneDrive, S3 Uploads plugin for WordPress is vulnerable to Arbitrary File Write in all…nvd.nist.gov ·
  • WordPress
  • CVE-2026-120522
  • Path traversal
  • Remote code execution
  • Plugin security