Gravity Forms <= 3.1.2 - Unauthenticated Stored Cross-Site Scripting via List Field
- Last modified
- Where the record stands: published, rejected by its publisher, or superseded by another id.What do these mean? →
- published
- Whether CISA lists it in its Known Exploited Vulnerabilities catalog: proof that attackers are using it.What do these mean? →
- Not listed in CISA KEV
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
- Exploitation: none
- Automatable: yes
- Technical impact: partial
Summary
The Gravity Forms plugin for WordPress is affected by a stored cross-site scripting flaw in its List Field feature, which lets an unauthenticated attacker plant malicious scripts that run in a user's browser. If an administrator is tricked into clicking an injected link in the entry details view and confirming a dialog, the attacker's script can run with that administrator's privileges.
Summarized by anthropic/claude-haiku-5.5. Verify details against the original sources.
Read the original description
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.
Timeline
- CVE published
- First seen by cve.now
- CISA SSVC assessment
Exploitation: none · Automatable: yes · Technical impact: partial
- Record last updated
Affected versions
- Gravity Forms Gravity Forms
through 3.1.2