Quick answers
- Is CVE-2026-19513 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-19513 being exploited in the wild.
- How severe is CVE-2026-19513?
- High severity, with a CVSS score of 8.1, published 1 September 2026.
- Which products and versions are affected?
- Rocketgenius Gravity Forms up to and including 3.0.2.
- Is there a fix for CVE-2026-19513?
- A patch was published on 2026-08-25: Patched in version 3.1.0; also patched in 3.0.3 Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-19513 attacked?
- It is attacked over the network.
- Am I affected by CVE-2026-19513?
- Check whether you run Rocketgenius Gravity Forms at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
Technical details
The vulnerability exists in the GFAsyncUpload::upload() function due to insufficient validation of multi-file upload chunk state. Attackers can exploit this by reusing public form state URL hashes as chunk continuation hashes and injecting attacker-controlled temporary filenames that bypass sanitization. When a public form contains a File Upload field with "Multiple Files" enabled, an unauthenticated attacker can upload a PNG/PDF polyglot file to an attacker-selected .php or .html filename in the plugin's temporary upload directory. On non-.htaccess-respecting web servers (such as NGINX), this results in remote code execution; on Apache with .htaccess present, stored cross-site scripting (XSS) becomes the primary risk. The attack requires no authentication and can be performed against any WordPress site using the vulnerable plugin versions.
Affected products
- Rocketgenius Gravity Forms up to and including 3.0.2
Timeline
- 2026-09-01: disclosed
- 2026-08-25: patched: Patched in version 3.1.0; also patched in 3.0.3