Gravity Forms <= 3.0.2 - Unauthenticated Arbitrary File Upload via State/Chunk Hash Confusion

8.1
Unrestricted Upload of File with Dangerous Type
CVE CVE-2026-19513
CVSS 8.1 (High)
Publicly Published September 1, 2026
Last Updated September 1, 2026
Researchers Alex Thomas - Wordfence
Wordfence Argus - Wordfence

Description

The Gravity Forms plugin for WordPress is vulnerable to Arbitrary File Upload in all versions up to, and including, 3.0.2. This is due to insufficient validation of multi-file upload chunk state in the `GFAsyncUpload::upload()` function, where public form state URL hashes can be reused as chunk continuation hashes and attacker-controlled temporary filenames are accepted before sanitization. This makes it possible for unauthenticated attackers, when a public form contains a File Upload field with Multiple Files enabled, to upload a valid PNG/PDF polyglot to an attacker-selected public `.php` or `.html` filename in the Gravity Forms temporary upload directory. This can lead to remote code execution on WordPress systems that use NGINX or other non `.htaccess` respecting web servers. NOTE: During installation and activation, the Gravity Forms plugin places a `.htaccess` file in this directory, which prevents this vulnerability from being exploited despite the PHP file being written to the temporary upload directory. In these cases where PHP execution is blocked, attacker-written HTML can result in stored same-origin cross-site scripting if a victim visits the generated file URL.

Learn more about Arbitrary File Upload vulnerabilities and how to prevent them.

References

Share

Vulnerability Details for Gravity Forms

Software Type Plugin
Software Slug gravityforms
Patched? Yes
Remediation Update to version 3.0.3, or a newer patched version
Affected Version
  • <= 3.0.2
Patched Version
  • 3.0.3

Recent vulnerabilities in Gravity Forms

# Title CVE ID CVSS Researchers Date
1 Gravity Forms <= 2.10.5 - Unauthenticated Stored Cross-Site Scripting via Post Body Field Value CVE-2026-16649 7.2 daroo September 4, 2026
2 Gravity Forms <= 2.10.4 - Unauthenticated Arbitrary File Read via 'gform_uploaded_files' Parameter CVE-2026-12997 7.5 daroo July 15, 2026
3 Gravity Forms <= 2.10.0.1 - Unauthenticated Arbitrary File Deletion CVE-2026-48866 9.1 daroo June 1, 2026
4 Gravity Forms <= 2.10.0 - Unauthenticated Stored Cross-Site Scripting via Single Product Field Inside Repeater CVE-2026-5110 7.2 Luc Huynh from Noventiq RedTeam May 1, 2026
5 Gravity Forms <= 2.10.0 - Unauthenticated Stored Cross-Site Scripting via Product Option CVE-2026-5109 7.2 Luc Huynh from Noventiq RedTeam May 1, 2026
6 Gravity Forms <= 2.9.30 - Unauthenticated Stored Cross-Site Scripting via Consent Field Hidden Input CVE-2026-5113 7.2 Luc Huynh from Noventiq RedTeam May 1, 2026
7 Gravity Forms <= 2.10.0 - Unauthenticated Stored Cross-Site Scripting via Hidden Product Field in Repeater CVE-2026-5111 7.2 Luc Huynh from Noventiq RedTeam May 1, 2026
8 Gravity Forms <= 2.10.0 - Unauthenticated Stored Cross-Site Scripting via Calculation Product Field in Repeater CVE-2026-5112 7.2 Luc Huynh from Noventiq RedTeam May 1, 2026
9 Gravity Forms <= 2.9.30 - Unauthenticated Stored Cross-Site Scripting via Credit Card 'Card Type' Sub-Field CVE-2026-4394 6.1 Luc Huynh from Noventiq RedTeam April 7, 2026
10 Gravity Forms <= 2.9.30 - Reflected Cross-Site Scripting via 'form_ids' Parameter CVE-2026-4406 4.7 Anthony Cihan (Hann1bl3L3ct3r) April 7, 2026

Did you know Wordfence Intelligence provides free personal and commercial API access to our comprehensive WordPress vulnerability database, along with a free webhook integration to stay on top of the latest vulnerabilities added and updated in the database? Get started today!

Learn more

Want to get notified of the latest vulnerabilities that may affect your WordPress site?
Install Wordfence on your site today to get notified immediately if your site is affected by a vulnerability that has been added to our database.

Get Wordfence

The Wordfence Intelligence WordPress vulnerability database is completely free to access and query via API. Please review the documentation on how to access and consume the vulnerability data via API.

Documentation