CVE-2026-120522: Contain Cloud Storage Manager's file-write flaw
If you run Cloud Storage Manager for Fluent Forms 1.2.0 or earlier, disable the affected plugin while arranging an update. CVE-2026-120522 allows an unauthenticated attacker to write files outside the intended download directory. A PHP file placed where the web server executes it can lead to remote code execution. Wordfence’s CNA record rates the flaw 9.8 Critical under CVSS 3.1.
What is affected
The affected WordPress plugin has the directory slug cloud-storage-manager. The CNA covers all versions through 1.2.0. Its description connects missing authorization checks with unsafe handling of filenames returned by Google Drive. This is a flaw in the WordPress integration, not a claim that Google Drive itself is vulnerable.
The CNA records disclosure on November 14, 2026 at 00:23:38 UTC and CVE publication at 12:33:22 UTC that day. Its vector is CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H. The record does not establish exploitation in the wild.
Choose an update without guessing the first fixed release
The WordPress plugin directory lists version 1.2.9 on November 14. Its changelog mentions API security hardening in 1.2.5. That wording alone does not prove which release first fixed this CVE.
The CNA marks versions outside its affected range as unaffected and references WordPress changeset 3656663. The changeset and the separate Wordfence advisory page returned access errors during verification, so this article does not name a first patched version. Ask the developer or hosting provider to confirm the release or backport that addresses CVE-2026-120522, then use the current supported package from a trusted source.
Updating Linux packages does not update this WordPress plugin. If a provider maintains a backport under an older version string, obtain its CVE-specific patch confirmation before treating the installation as repaired.
Contain, update and check normal uploads
Check the plugin’s installed version and activation status in WordPress administration, including any network activation on multisite installations you manage. Coordinate the interruption with the person responsible for form submissions: disabling the integration can interrupt cloud uploads.
- Deactivate the affected plugin promptly. Preserve form records, configuration and a recoverable backup; do not delete submission data as a workaround.
- Review the exposed site’s files and relevant access logs. Investigate unexpected executable files and unapproved changes to plugin connections. Preserve evidence securely if you suspect compromise.
- Install the confirmed fixed, supported release through your normal WordPress update process. Test it on a staging copy before restoring the integration where practical.
- Confirm the installed version and activation state, then submit a harmless test attachment through an authorized test form. Check that it reaches the intended storage account and that normal upload failures remain visible to the administrator.
These checks confirm configuration and ordinary behavior, not absence of compromise. An update does not remove a file an attacker already wrote. If you find suspicious changes, involve your incident responder before restoring service and replace exposed credentials through the relevant providers’ approved process. Do not include credentials or form attachments in public tickets.
Inspect the CVE record from Linux
The following example downloads public metadata only. It sends no request to a WordPress site and does not exercise the vulnerable file-writing path. Use Bash, curl and Python 3.
Create a scratch directory, then stay in the same terminal session. Stop if setup fails.
advisory_dir=$(mktemp -d ./cloud-storage-advisory.XXXXXX) &&
cd -- "$advisory_dir"Save this source as inspect-cloud-storage-record.py:
import json
from pathlib import Path
import sys
record = json.loads(Path(sys.argv[1]).read_text(encoding="utf-8"))
metadata = record["cveMetadata"]
if metadata["cveId"] != "CVE-2026-120522":
raise SystemExit("Expected CVE-2026-120522")
cna = record["containers"]["cna"]
score = cna["metrics"][0]["cvssV3_1"]
print("CVE:", metadata["cveId"])
print("CNA:", metadata["assignerShortName"])
print("Disclosed (UTC):", cna["timeline"][0]["time"])
print("Published (UTC):", metadata["datePublished"])
print("CVSS:", score["version"], score["baseScore"], score["baseSeverity"])
for product in cna["affected"]:
for version in product["versions"]:
if version["status"] == "affected":
print("Affected through:", version["lessThanOrEqual"], "(inclusive)")
print("Metadata only; no WordPress site was tested.")Download the record and run the helper:
curl --fail --silent --show-error --max-time 30 \
'https://cveawg.mitre.org/api/cve/CVE-2026-120522' \
--output cloud-storage-cve.json &&
python3 inspect-cloud-storage-record.py cloud-storage-cve.jsonActual output on Debian 13 with Python 3.12.14, November 14, 2026:
CVE: CVE-2026-120522
CNA: Wordfence
Disclosed (UTC): 2026-11-14T00:23:38.000Z
Published (UTC): 2026-11-14T12:33:22.808Z
CVSS: 3.1 9.8 CRITICAL
Affected through: 1.2.0 (inclusive)
Metadata only; no WordPress site was tested.The helper expects this record’s current structure. It does not compare your installed plugin with a fixed release. Save the JSON and its retrieval date elsewhere if you need an incident record, because the public record can change.
From the same scratch directory, this optional cleanup removes only the two example files and their empty directory:
rm -- inspect-cloud-storage-record.py cloud-storage-cve.json &&
cd .. &&
rmdir -- "$advisory_dir" &&
unset advisory_dirSetup and cleanup completed without output. No WordPress installation, plugin update or exploit was tested.
This post was created with assistance from AI.