← All security briefings

Attention

Cloud Storage Manager for Fluent Forms 1.2.0 and earlier: unauthenticated file write via Google Drive filename path traversal (CVE-2026-120522)

Identifiers: CVE-2026-120522

Published
Last substantive change
Last verified

Last verified: . Attention items are due for re-verification within 72 hours.

Summary

On 14 November 2026 Wordfence disclosed CVE-2026-120522 in Cloud Storage Manager for Fluent Forms. In 1.2.0 and earlier, a REST route lacks an authorization check. An unauthenticated attacker can store their own Google Drive credentials in the plugin and trigger a download from a Drive they control. The filename returned by the provider is not confined to the intended downloads folder, so a crafted name can place a file elsewhere on the server. Remote code execution follows only if a PHP file lands in a web-accessible, executable location. Fixed in 1.2.5; the vendor's current release is 1.2.9.

Classification reason: Checked 14 November 2026. Public disclosure by Wordfence on 14 November 2026. Vendor fix 1.2.5 exists and 1.2.9 is current. No exploitation established in reviewed sources.

Impact

Arbitrary file write on the web server. The worst case is full site takeover through a planted script. Lesser outcomes include overwritten files or a broken site. According to the researcher, the attack does not need the victim's existing Drive connection or credentials. Not every Fluent Forms setup or cloud provider path is identical; the disclosed issue concerns the Google Drive download path.

Who is affected

Sites with Cloud Storage Manager for Fluent Forms active at 1.2.0 or earlier. Per the researcher, having Google Drive already connected is not a prerequisite. Server file permissions and PHP execution limits in upload directories change the severity but have not been verified as protection.

Products and versions

Products and versionsAffectedFixed
Cloud Storage Manager for Fluent Forms <= 1.2.0 1.2.5

Exploitation evidence

Exploitation not established. No exploitation in the wild is established in reviewed Wordfence, vendor, or KEV sources as of 14 November 2026. The attack is unauthenticated and, per the researcher, needs no victim credentials. Code execution depends on where the written file lands. Technical exploitation details are deliberately not reproduced here.

Sources: Wordfence Intelligence, CISA

Actions

  1. Update to 1.2.5 or newer (vendor current 1.2.9) and confirm the active version on the Plugins screen.
  2. Submit a test form with a file upload and confirm the file reaches your cloud folder as expected.
  3. Review the plugin's connected cloud account: confirm it is yours, check sharing settings, and look through the provider's recent activity log for unfamiliar access.
  4. Do not ask site users or staff for their personal cloud credentials as part of this response. Only the plugin's own connection matters.
  5. If you have reason to suspect compromise, look for unexpected files in wp-content and other writable directories and plan a bounded recovery: restore from a known-good backup and rotate secrets. The update does not prove the site was clean beforehand.
  6. If you cannot update, deactivate the plugin and ask your provider. Before pausing it, check how deactivation affects your form uploads, where submitted files are kept, and whether they are still delivered, because that depends on your configuration and was not verified here. No configuration workaround has been verified as equivalent to the vendor fix.

Unknowns

  • The technical description rests primarily on Wordfence. The vendor's 1.2.5 changelog says "security hardening at the API level", which confirms a release described as security hardening exists but does not independently confirm the fix, the exact affected range, or the mechanism.
  • The CVE record at the CNA returned 404 and the WordPress.org Trac changeset returned 403 at check time. These are coverage gaps, not contradicting evidence.
  • No in-the-wild exploitation was found in reviewed Wordfence, vendor, or CISA KEV sources. Absence of a report is not proof that none has occurred.
  • Whether the Dropbox path or Pro providers share the same weakness was not stated in the reviewed sources.

Sources

  • Wordfence Intelligence · retrieved https://www.wordfence.com/threat-intel/vulnerabilities/wordpress-plugins/cloud-storage-manager/cloud-storage-manager-for-fluent-forms-120-unauthenticated-arbitrary-file-write-via-google-drive-filename-path-traversal
  • Plugin vendor via WordPress.org SVN · retrieved https://plugins.svn.wordpress.org/cloud-storage-manager/trunk/readme.txt
  • CISA · retrieved https://www.cisa.gov/sites/default/files/feeds/known_exploited_vulnerabilities.json

Change history

  1. — Published: 14 November 2026: briefing created from the Wordfence disclosure of CVE-2026-120522 in Cloud Storage Manager for Fluent Forms. Affected 1.2.0 and earlier, fixed in 1.2.5, vendor current 1.2.9. No exploitation established.

Subscribe: RSS feed · JSON Feed · Feed format and fields