Live Exposure Defense: From CVE to Confirmed Exposure in 12 Hours – See more

New CVE Detected

CVE-2026-19513 – Unauthenticated Arbitrary File Upload (RCE) – Gravity Forms ≤ 3.0.2

Be the first to know when new zero-days emerge:

Summary

CVE-2026-19513 is an unauthenticated arbitrary file upload vulnerability in the Gravity Forms plugin for WordPress, affecting all versions up to and including 3.0.2. The flaw resides in the GFAsyncUpload::upload() function and, on servers that do not restrict script execution in the uploads directory, can lead to remote code execution; on other configurations it can result in stored cross-site scripting. The issue carries a CVSS v3.1 base score of 8.1 (High).

Technical details

  • Root cause: Insufficient validation in GFAsyncUpload::upload() allows confusion between public form "state" URL hashes and chunk continuation hashes, combined with unvalidated temporary filenames.
  • Trigger conditions: A public-facing form must include a multi-file File Upload field; no authentication is required to exploit it.
  • Attack vector: Network — an attacker submits crafted chunked upload requests to a public form, reusing state hashes as chunk hashes to write PNG/PDF polyglot files with .php or .html extensions into the temporary upload directory.
  • Impact: On servers lacking .htaccess-style execution protection (e.g., NGINX configurations without equivalent hardening), this can lead to remote code execution; on servers where the uploaded file cannot execute, it can result in stored cross-site scripting.

Affected software

  • Gravity Forms (WordPress plugin) — all versions up to and including 3.0.2

Severity

  • CVSS v3.1 Base Score: 8.1 (High)
  • Vector: CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H

Mitigation and recommended actions

  • Immediate: Upgrade Gravity Forms to version 3.0.3 or later, which contains security fixes for this issue.
  • If patching is delayed: Ensure the web server blocks execution of scripts (e.g., .php, .html) within the WordPress uploads/temporary upload directories, and restrict or monitor public forms that use multi-file File Upload fields until patched.

How IONIX identifies potentially affected assets

IONIX matches the following signals against data already collected when it crawled the asset; identifying the technology sends no request beyond that crawl.

  • Raw response body: <div class="gform_wrapper, <div class="gform_body, <ul class="gform_fields, <link href="wp-content/plugins/gravityforms/css/
  • URL of a loaded script: /wp-content/plugins/gravityforms/js/*.js?ver=<version>

References

Are you exposed?

Get a free report of your organization’s exposure to this CVE and threat

How IONIX’s External Exposure Management Platform Detects and Validates
Zero-Days to Shrink MTTR

1

Map your entire attack surface (continously)

IONIX uses multi-factor discovery methods, including DNS analysis, certificate mapping, metadata inspection, and more, to automatically map every internet-facing asset across your environment. This includes cloud instances, third-party platforms, shadow IT, and even forgotten infrastructure that traditional tools miss.

2

Monitor for new CVEs

Dozens of threat intel feeds using agentic technology are continuously analyzed to detect the appearance of proof-of-concept code, exploit kits, and indicators of active targeting. IONIX goes further by applying AI to proactively evaluate whether emerging vulnerabilities are likely to be exploited, even before PoCs go public.

3

Identify Potential External Exposures

Not all CVEs matter. IONIX filters vulnerabilities by asking attacker-centric questions: Can it be reached from the internet? Does it require authentication? Is it being exploited in the wild? This dramatically reduces noise and focuses teams on threats that can actually be weaponized.

4

Create Safe, Scalable Exploit Validations

IONIX transforms real-world PoCs into safe, non-intrusive test payloads that can be run in production environments without disruption. These simulations are precisely targeted to the systems that are vulnerable, ensuring rapid validation without unnecessary load.

5

Execute Exploit Validations

By combining context about software stack, versioning, exposure status, and reachability, IONIX ensures that only the right payloads are executed against the right assets, maximizing efficiency and minimizing risk.

6

Drive Fast and Actionable Remediation

Results are routed through integrations with ticketing, SOAR, and SIEM tools. Issues are written in plain language, bundled into remediation clusters, and prioritized based on asset criticality, exploitability, and blast radius. This shortens mean time to remediation (MTTR) and empowers teams to act with confidence.

Are you exposed?

Get a free report of your organization’s exposure to this CVE and threat

Subscribe to Threat Center RSS

Copy/paste the link below into your preferred RSS reader or follow these instructions to subscribe to Slack alerts.

Get Real-Time CVE Alerts to Your Email

Be the first to know when new zero-days emerge