> ## Content Index
> Fetch the complete content index at: https://stackurity.ai/blog/llms.txt
> Use this file to discover other available public pages before exploring further.

# Fluent Forms Cloud Storage Manager flaw CVE-2026-120522: remove it
- URL: https://stackurity.ai/blog/fluent-forms-cloud-storage-manager-cve-2026-120522-arbitrary-file-write/
- Published: 2026-11-16T01:35:04.000Z
- Updated: 2026-11-16T01:35:04.000Z
- Description: A critical WordPress plugin flaw lets anyone write files to the server. See who is affected, how to check one site and how to mitigate it.
- Author: Stackurity Research Team
- Tags: Linux Servers, #deep-dive

## TL;DR

- What: the Cloud Storage Manager for Fluent Forms plugin for WordPress lets an unauthenticated attacker write a file anywhere the web server can reach, tracked as CVE-2026-120522.
- Impact: if the written file is a PHP file in a web-accessible folder, the attacker can run code on the server.
- Severity: a CVSS v3.1 score of 9.8 (critical) from Wordfence, with a network attack vector and no privileges needed.
- Exploited: we found no listing in the CISA Known Exploited Vulnerabilities catalogue, but the flaw was published only days ago.
- Fix: the advisory names no fixed version. Remove or deactivate the plugin until the vendor ships one, and check the vendor's page for the release.

## What the vulnerability is, in plain English

The Cloud Storage Manager for Fluent Forms plugin connects form uploads in WordPress to storage services such as Google Drive, Dropbox, OneDrive and S3\. The [NVD entry for CVE-2026-120522](https://nvd.nist.gov/vuln/detail/CVE-2026-120522) describes a flaw that lets files be written to places the plugin never meant, present in every release through 1.2.0\. It was published on November 14, 2026.

Two things combine. First, two REST endpoints, one that saves a storage connection and one that downloads a single file, do not check who is calling them. Anyone on the internet can use them. Second, when the plugin downloads a file from Google Drive, it takes the file name that Google Drive reports and adds it to a local path without cleaning it. A file name that contains path traversal, such as steps that climb out of the downloads folder, therefore lands somewhere else on the disk.

An attacker can put their own Google Drive credentials into the plugin, ask it to fetch a file they own, name that file so the path climbs out of the intended folder, and the server writes their content there. This weakness class is CWE-22, path traversal. Nothing in the attack needs a password or a visit from an administrator.

The step that turns this into a full takeover is the file type. NVD notes that a file ending in a PHP extension, saved where the web server will serve it, can give the attacker remote code execution. In practice, that means the attacker can run their own code with the permissions of the web server, read the site's configuration, reach the database and use the server as a base for more attacks.

## Why it matters now

This is a fresh flaw, and fresh flaws in WordPress plugins tend to be tried quickly, because the attacker does not need to know anything about your site. A scan for sites that have the plugin installed is enough. We have recently covered other WordPress plugin and core problems, including [a payment plugin flaw that was being targeted](https://stackurity.ai/blog/cryptopayment-gateway-cve-2026-81648-wordpress-plugin/), and the pattern is the same: the plugin is quiet until a public advisory turns it into a target.

The advisory records no fixed version, so you cannot simply check a box and move on. There is a code change linked from the advisory, which suggests the maintainers are aware, but you should confirm in the plugin's own listing and changelog that a release exists before you rely on it. Until then, the safe state for a site that does not need the plugin is a removed plugin.

Shops and form-heavy sites are the likely owners of this plugin, because uploads are its whole purpose. Those are also the sites that hold customer details and take payments, so a web shell on such a server is a bigger problem than a defaced page.

## Am I affected?

You are affected if a WordPress site has the Cloud Storage Manager for Fluent Forms plugin installed at version 1.2.0 or any earlier version. The plugin does not have to be in active use for its files to sit on the disk, so check installed plugins, not only active ones.

To check one server by hand, list the plugin folders of each WordPress install and read the plugin's version:

```
wp plugin list
wp plugin get cloud-storage-manager
```

If WP-CLI is not available, look in the plugins directory of the site for a folder named for the plugin and read the version in the main plugin file header. The folder name in the advisory references is `cloud-storage-manager`.

To look for signs of abuse, search the site for PHP files that you did not put there, especially in upload and download folders:

```
find wp-content/uploads -name '*.php' -ls
```

Treat a PHP file in an upload or download folder as suspicious until you can say where it came from. Also review web server logs for requests to the plugin's REST paths from addresses you do not recognise. Repeat the check for staging copies, because they are often forgotten and often just as exposed.

## How to mitigate CVE-2026-120522

1. List every WordPress site you run and find which have the Cloud Storage Manager for Fluent Forms plugin, in any state, installed at version 1.2.0 or earlier.
2. Check the plugin's page and changelog for a release newer than 1.2.0 that names this issue. The advisory we checked does not name a fixed version, so confirm it with the vendor before you rely on an update.
3. If a newer release exists, update every copy, then confirm the version you see on the server matches. If none exists, deactivate and delete the plugin from every site that can live without it.
4. If a site must keep the plugin, block the plugin's connection and download REST paths at the web server or the firewall until a fix is out, and deny PHP execution in upload and download folders.
5. Look for files that should not exist: new PHP files in upload and download folders, and changes to files outside the plugin's folder. If you find any, treat the site as compromised, restore from a clean backup and rotate the database password and the salts in the site configuration.

## How to check with Stackurity

The honest version first: Stackurity cannot tell you that a site is vulnerable to this flaw. It finds WordPress sites as applications, reading the site's configuration and version files, and lists plugins and themes with their latest release from wordpress.org, but plugin vulnerabilities are not matched yet. What it does give you, across every server and image, is the list of sites that have this plugin installed at all, which is the part that usually takes the most time.

Run the agent on your Linux servers, with the opt-in Docker option for images, and search the inventory for the plugin name. Each match tells you which server it lives on and which team owns it, so you can send the removal to the right person. After the change, Check again asks the agent for a fresh report, and the plugin should no longer appear. To confirm the web server is not serving stray PHP files, use the file check above on the same machines.

Stackurity also finds keys and passwords written in files, which matters after any web shell: if a site was compromised, the keys on that server should be treated as exposed. Read how the [remediation workflow](https://stackurity.ai/docs/remediation) tracks a fix until it is verified. [Start a free trial of Stackurity](https://app.stackurity.dev/signup?utm%5Fsource=blog&utm%5Fmedium=referral&utm%5Fcampaign=linux-servers&utm%5Fcontent=fluent-forms-cloud-storage-manager-cve-2026-120522-arbitrary-file-write) and see which of your sites carry the plugin.

## FAQ

### What is CVE-2026-120522?

It is a critical flaw in the Cloud Storage Manager for Fluent Forms plugin for WordPress. An attacker who is not logged in can make a site write a file of their choosing outside the folder meant for downloads, and a file with a PHP extension in a web-accessible place can lead to remote code execution.

### Which versions of the plugin are affected?

Every release through 1.2.0\. The advisory we checked does not name a fixed version, so read the plugin's page and the vendor's changelog for the release that closes the hole.

### Is CVE-2026-120522 being exploited?

We found no sign of it in the CISA Known Exploited Vulnerabilities catalogue at the time of writing. That can change, and the attack needs no login, so do not treat the lack of a listing as safety.

### Does Stackurity find this plugin flaw?

Not yet. Stackurity finds WordPress sites and lists their plugins with the latest release from wordpress.org, but it does not match plugin vulnerabilities yet. It is a way to see which sites have the plugin installed, not a confirmation that a site is vulnerable.

### What should I do if I cannot update the plugin?

Deactivate and remove it until a fixed release is available. If it must stay, block the two REST paths named in the advisory at your web server or firewall, and check the plugin's folders for PHP files that should not be there.

## Sources

Sources: [NIST National Vulnerability Database entry for CVE-2026-120522](https://nvd.nist.gov/vuln/detail/CVE-2026-120522) and the [Stackurity product facts](https://stackurity.ai/llms.txt).