Live › vulnerability › CVE-2026-97645
The Gravity Forms WordPress plugin up to and including 3.1.2 does not sanitize List Field input or escape its output. An unauthenticated attacker can store a script that runs in the browser of an administrator who opens the entry and confirms a dialog.
Summary written from the sources below. Check the originals before acting.
First seen by InfraStack 2026-10-30 07:29 UTC. All times on this page are UTC.
WordPress sites running Gravity Forms 3.1.2 or earlier. Exposure needs a public form with a List Field, since an unauthenticated visitor can store a script in an entry. It runs only when an administrator opens the entry, clicks the injected link and confirms a dialog. Sites without List Field forms, or on 3.1.3+, can skip it.
| Product | Ecosystem | Affected | Fixed in |
|---|---|---|---|
| Gravity Forms | wordpress | <= 3.1.2 | 3.1.3 |
3.1.2 or earlier is affectedUpdate Gravity Forms to 3.1.3 or later (WordPress admin > Plugins > Update).
Each row is the first time that source carried this signal. The analyst’s rows are its own findings.
The Gravity Forms plugin for WordPress is vulnerable to Stored Cross-Site Scripting via List Field in all versions up to, and including, 3.1.2 due to insufficient input sanitization and output escaping. This makes it possible for unauthenticated attackers to inject arbitrary web scripts in pages that will execute whenever a user accesses an injected page. Successful exploitation requires the administrator to click the injected link in the entry detail view and confirm a dialog, which triggers the admin JavaScript bundle's delegated data-dialog-callback handler to invoke the attacker-supplied function reference.
This page as .md · .json · in your agent: get_signal("CVE-2026-97645")
NVD data is provided by NIST and is public domain. Posts quoted belong to their authors.