# CVE-2026-19513: Gravity Forms <= 3.0.2 - Unauthenticated Arbitrary File Upload via State/Chunk Hash Confusion


- **Severity:** High 8.1 (`CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Fix available:** No
- **Published:** 1 Sep 2026
- **Updated:** 1 Sep 2026
- **Also known as:** GHSA-fjj9-76vm-r7vp

## What is CVE-2026-19513?

CVE-2026-19513 is a high-severity vulnerability in Gravity Forms, published on 1 Sep 2026. 

### Official 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.

Weakness: CWE-434 (Unrestricted Upload of File with Dangerous Type)

## Which versions are affected by CVE-2026-19513?


## How do I fix CVE-2026-19513?

No fix has been published for CVE-2026-19513 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-19513 being exploited?

There is no known exploitation of CVE-2026-19513 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-19513 and fix it if it is affected.

What it is: CVE-2026-19513 is a high-severity vulnerability in Gravity Forms, published on 1 Sep 2026. 
Exploitation: There is no known exploitation of CVE-2026-19513 in the wild and no public exploit code.

Affected product: Gravity Forms. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-19513/ (Markdown: https://insights.sbomify.com/CVE-2026-19513/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-19513
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-19513
- OSV: https://osv.dev/vulnerability/CVE-2026-19513

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-19513/
Summaries are generated and may contain mistakes; the official description above is the record.