CVE-2026-19513
Last modified
CVE-2026-19513 is a high-severity vulnerability rated 8.1/10 on the CVSS scale. 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.
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.
Metrics
Weakness Enumeration
Affected Software
Source: CNA advisory (CVE.org). NVD analysis pending.
| Vendor | Product | Versions |
|---|---|---|
| Gravity Forms | Gravity Forms | <= 3.0.2 |
References
Timeline
- Published
- Last Modified
- Status
- Deferred
Frequently Asked Questions
What is CVE-2026-19513?
How severe is CVE-2026-19513?
How do I fix CVE-2026-19513?
How Strix Helps
- How Strix found a critical auth bypass in etcdStrix autonomously discovered a critical authentication bypass in etcd, later designated CVE-2026-33413.
- Autonomous PentestingAI agents that find and validate exploitable vulnerabilities like this one across your applications.
- PR ReviewsPentest every pull request so vulnerable code is caught before it ships to production.
- AI Penetration TestingHow AI-driven penetration testing continuously covers your attack surface.
Related CVEs from 2026
- CVE-2026-19505Improper cryptographic signature verification in `jst_functi…9.8
- CVE-2026-19506Race condition in `check.jst` in RDK-B WebUI `rdkb-2025q4-ki…8.1
- CVE-2026-19507Uncontrolled resource consumption in `check.jst` in RDK-B We…7.5
- CVE-2026-19508Heap-based buffer overflow in the multipart form-data parser…9.8
- CVE-2026-19509Improper input validation in `ajaxSet_wireless_network_confi…6.5
- CVE-2026-1951Delta Electronics AS320T has no checking of the length of th…9.8
- CVE-2026-19516A caller-supplied X-Grafana-URL request header controls the …9.1
- CVE-2026-19517Improper Validation of Specified Quantity in Input and Alloc…6.5
- CVE-2026-19518Improper Validation of Specified Quantity in Input vulnerabi…6.5
- CVE-2026-19519A flaw was found in claircore's RPM package scanner. Crafted…4.3
- CVE-2026-1952Delta Electronics AS320T has denial of service via the undoc…7.5
- CVE-2026-1953Nukegraphic CMS v3.1.2 contains a stored cross-site scriptin…8.2
Are you affected by CVE-2026-19513?
Run a free Strix scan to check your systems for this vulnerability.
Scan your code nowSource: NVD / NIST
