CVE-2026-19513
Unauthenticated arbitrary file upload in Gravity Forms allows RCE on non-.htaccess servers
Is CVE-2026-19513 being exploited?
Not confirmed. CVE-2026-19513 does not appear in CISA's Known Exploited Vulnerabilities catalog, which records only exploitation that has been observed and reported publicly. That is evidence of absence of a report, not evidence the flaw is unattacked. EPSS currently estimates a 0.50% probability of exploitation in the next 30 days.
How severe is CVE-2026-19513?
CVE-2026-19513 is rated High with a CVSS score of 8.1. Severity describes how bad exploitation would be, not how likely it is: pair it with exploitation evidence before deciding what to patch first.
Is there a patch for CVE-2026-19513?
Yes. A fix has been recorded for CVE-2026-19513. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.
What does CVE-2026-19513 affect?
CVE-2026-19513 affects Gravity Forms <= 3.0.2, WordPress sites using Gravity Forms, Sites with public File Upload field (Multiple Files enabled), NGINX or other non-.htaccess web servers. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.
What should I do about CVE-2026-19513?
Upgrade Gravity Forms to patched version; disable public multi-file uploads; block script execution in upload dir.
Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.
Unauthenticated arbitrary file upload can lead to remote code execution on NGINX/non-.htaccess servers; stored same-origin XSS if PHP execution is blocked.
Immediate action required
- affected<= 3.0.2
As published in the CVE Program record. A version outside these ranges is not a statement that it is unaffected — vendors sometimes understate a range, and distribution-backported builds carry upstream numbers that do not reflect what was patched into them.