CVE-2026-87796

9.8

sh1zen · Multi Uploader for Gravity Forms

The Multi Uploader for Gravity Forms plugin for WordPress is vulnerable to arbitrary file uploads via the move_file function due to insufficient validation, potentially allowing remote code execution.

Executive summary

An unauthenticated arbitrary file upload vulnerability in the sh1zen Multi Uploader for Gravity Forms plugin poses a critical risk of remote code execution.

Vulnerability

This vulnerability occurs due to insufficient file type validation during chunked upload handling within the move_file function. An unauthenticated attacker can leverage this flaw to upload malicious files to the server, which can subsequently be executed to achieve remote code execution.

Business impact

The vulnerability carries a CVSS score of 9.8, indicating a critical severity level. Successful exploitation grants an attacker full control over the affected server, potentially leading to total system compromise, data exfiltration, and significant service disruption.

Remediation

Immediate Action: There is currently no confirmed patch available for this vulnerability. Administrators should immediately deactivate or uninstall the Multi Uploader for Gravity Forms plugin until a secure version is released by the vendor.

Proactive Monitoring: Review web server access logs for suspicious file upload requests, particularly those targeting the plugin's upload directory or unusual file extensions.

Compensating Controls: Deploy a Web Application Firewall (WAF) with rules configured to block unauthorized file uploads and inspect incoming HTTP requests for common malicious file signatures.

Exploitation status

Public Exploit Available: No (unknown)

Analyst recommendation

Given the critical nature of this vulnerability and the lack of a vendor-provided patch, immediate removal or deactivation of the plugin is the only effective way to mitigate risk. Organizations should prioritize this task to prevent potential remote code execution attacks against their infrastructure.

History

  1. Disclosed CVE record published
  2. Collected by CVE Brief via github
  3. Analyst report written
  4. Analyst report updated
  5. Published in the daily brief critical section

Sources

Originally found and disclosed by Adam Rayyan Aryasatya, per the CVE Program record.