CVE-2026-90437

Gravity Forms <= 3.1.1 - Unauthenticated Stored Cross-Site Scripting via Post Excerpt / Post Custom Field / Rich-Text Paragraph Field Values

Published Oct 30, 2026 CVSS 3.1 · 7.2 High EPSS < 1% KEV · Not listed
Description
The Gravity Forms plugin for WordPress is vulnerable to Stored Cross-Site Scripting via Post Excerpt / Post Custom Field / Rich-Text Paragraph Field Values in all versions up to, and including, 3.1.1 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. This is possible because Post Excerpt, Post Custom Field, and Rich-Text-Editor-enabled Paragraph Text fields allow raw HTML submissions via allow_html(), and an entity-encoded payload stored in a data-dialog-confirm attribute evades wp_kses_post() at save time but is decoded into executable markup by the browser when the plugin's admin JavaScript passes the attribute value to insertAdjacentHTML().

Analysis

AI-generated

Technical impact

Gravity Forms processes certain field types—Post Excerpt, Post Custom Field, and Rich‑Text Paragraph fields—without proper sanitization of raw HTML. Attackers can embed arbitrary web scripts that are saved to the database and later rendered by the plugin’s admin JavaScript. When a user loads a page containing the stored payload, the browser executes the script, enabling defacement, cookie theft, session hijacking, and other client‑side attacks. This flaw corresponds to the Common Weakness Enumeration CWE‑79.

Affected Systems

The vulnerability affects all installations of the Gravity Forms WordPress plugin version 3.1.1 and earlier. Any site that hosts forms with the aforementioned field types and allows raw HTML input is susceptible. The problem manifests both on the admin side—while the data is submitted—and on the public pages that display the stored content.

Risk and Exploitability

The CVSS score of 7.2 classifies this as a high‑severity flaw, and the lack of authentication requirements means an attacker can exploit it without privileged access. Although no EPSS value is available and the issue is not listed in CISA KEV, the stored‑XSS nature of the exploit and the widespread use of Gravity Forms make this a realistic threat for exposed WordPress sites. An attacker simply submits malicious payloads through a public form or via the plugin’s backend interface to implant scripts that will run for any subsequent visitor to the affected page.

Remediation

No solution or workaround provided in the CVE record.

OpenCVE Recommended Actions

  • Upgrade the Gravity Forms plugin to version 3.1.2 or later, which includes proper input sanitization and output escaping for the affected fields.
  • If an upgrade cannot be performed immediately, disable raw HTML input for Post Excerpt, Post Custom Field, and Rich‑Text Paragraph fields by removing allow_html() or configuring the plugin to strip disallowed tags.
  • Audit all existing form submissions for embedded scripts, remove or sanitize any malicious content, and verify that displayed values are rendered safely.

Generated by OpenCVE AI on October 30, 2026 at 08:23 UTC.

Tracking

Sign in to view the affected projects.

Advisories

No advisories available
History
Type Values Removed Values Added
First Time appeared Gravityforms
Gravityforms gravity Forms
Wordpress-extensions
Wordpress-extensions gravity Forms
Vendors & Products Gravityforms
Gravityforms gravity Forms
Wordpress-extensions
Wordpress-extensions gravity Forms
Type Values Removed Values Added
Metrics ssvc

{'options': {'Automatable': 'yes', 'Exploitation': 'none', 'Technical Impact': 'partial'}, 'version': '2.0.3'}

Type Values Removed Values Added
Description The Gravity Forms plugin for WordPress is vulnerable to Stored Cross-Site Scripting via Post Excerpt / Post Custom Field / Rich-Text Paragraph Field Values in all versions up to, and including, 3.1.1 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. This is possible because Post Excerpt, Post Custom Field, and Rich-Text-Editor-enabled Paragraph Text fields allow raw HTML submissions via allow_html(), and an entity-encoded payload stored in a data-dialog-confirm attribute evades wp_kses_post() at save time but is decoded into executable markup by the browser when the plugin's admin JavaScript passes the attribute value to insertAdjacentHTML().
Title Gravity Forms <= 3.1.1 - Unauthenticated Stored Cross-Site Scripting via Post Excerpt / Post Custom Field / Rich-Text Paragraph Field Values
Weaknesses CWE-79
References
Metrics cvssV3_1

{'score': 7.2, 'vector': 'CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:L/I:L/A:N'}

Weaknesses
  • CWE-79

    Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting')

Sources

Status
PUBLISHED
Assigner
Wordfence
Published
Updated
Oct 30, 2026, 6:09 PM
Reserved
Sep 11, 2026, 7:59 PM
Status
Deferred
Published
Oct 30, 2026, 7:16 AM
Modified
Oct 30, 2026, 7:20 PM