Gravity Forms <= 2.9.21.1 - Unauthenticated Arbitrary File Upload via Legacy Chunked Upload
Strategic Overview
- Status
- Patched in 2.9.22
- Affected Plugin
- Gravity Forms
- Affected Version
<= 2.9.21.1- CVSS
- 8.1High
- Weakness type
- CWE-434 · Unrestricted Upload of File with Dangerous Type
- CVE
CVE-2025-12974
At a glance
CVE-2025-12974 is a high-severity Unrestricted Upload of File with Dangerous Type vulnerability in the Gravity Forms WordPress plugin, affecting versions <= 2.9.21.1. It carries a CVSS score of 8.1 (reachable over the network; high confidentiality, integrity, availability impact). Exploitation requires no authentication. The issue is fixed in version 2.9.22; sites on affected versions should update now. Disclosed November 2025, reported by Talal Nasraddeen.
Vulnerability Overview
The Gravity Forms plugin for WordPress is vulnerable to arbitrary file uploads due to missing file type validation in the legacy chunked upload mechanism in all versions up to, and including, 2.9.21.1. This is due to the extension blacklist not including .phar files, which can be uploaded through the chunked upload mechanism. This makes it possible for unauthenticated attackers to upload executable .phar files and achieve remote code execution on the server, granted they can discover or enumerate the upload path. In order for an attacker to achieve RCE, the web server needs to be set up to process .phar file as PHP via file handler mapping or similar.
Technical Analysis
The vector marks this flaw as remotely reachable over the network, and no privileges on the target site, and no interaction from a victim user. A successful exploit has high impact on confidentiality, integrity, availability — full site compromise territory.
CWE-434: Unrestricted Upload of File with Dangerous Type
Reaching this weakness in Gravity Forms <= 2.9.21.1 takes no account at all. An unrestricted file upload lets a caller store a file whose type or destination the application does not properly constrain.
If an uploaded file lands anywhere the server will execute, the flaw becomes remote code execution and the site should be treated as fully compromised. For Gravity Forms the fix is 2.9.22: builds <= 2.9.21.1 are affected, anything from 2.9.22 onward is not.
Remediation
Update to version 2.9.22, or a newer patched version
How does WordSec protect against this?
Requests carrying this pattern arrive without a session, so nothing upstream of the firewall gets a chance to reject them: WordSec's web application firewall inspects request payloads before WordPress loads them. Classes like this one can leave something behind, so the staged malware scanner is the second half: it looks for dropped files and modified code rather than for the request that created them. None of that substitutes for the fix: Gravity Forms 2.9.22 closes this, and updating the plugin is the step that ends it.
- Firewall
- Scanner
- Login Security
External References
Related records
Same weakness class
Other vulnerabilities in Gravity Forms
- 9.8CVE-2023-28782: Gravity Forms <= 2.7.3 PHP Object Injection
CVE-2023-28782 - 9.1CVE-2026-48866: Gravity Forms <= 2.10.0.1 Arbitrary File Deletion
CVE-2026-48866 - 9.1CVE-2015-2260: Gravityforms <= 1.9.3.5 SQL Injection
CVE-2015-2260 - 7.5CVE-2026-12997: Gravity Forms <= 2.10.4 Arbitrary File Read
CVE-2026-12997 - 7.5CVE-2020-13764: Gravityforms <= 2.4.8 Information Exposure
CVE-2020-13764 - 7.2CVE-2026-16649: Gravity Forms <= 2.10.5 Stored Cross-Site Scripting
CVE-2026-16649 - 7.2CVE-2026-5113: Gravity Forms <= 2.9.30 Stored Cross-Site Scripting
CVE-2026-5113 - 7.2CVE-2026-5112: Gravity Forms <= 2.10.0 Stored Cross-Site Scripting
CVE-2026-5112
Vulnerability data © Defiant, Inc., provided under the Wordfence Intelligence T&C