CVE-2026-5111
HighSummary
The Gravity Forms plugin for WordPress is vulnerable to Stored Cross-Site Scripting in versions up to and including 2.10.0. The issue arises from insufficient input validation and output escaping on Hidden Product field values, allowing unauthenticated attackers to inject scripts.
Risk Assessment
Attackers can inject malicious scripts that will execute when an administrator views entry details, potentially leading to data theft or account takeover.
Recommendation
It is recommended to update the Gravity Forms plugin to the latest version to mitigate this vulnerability and to review and validate all forms to secure against similar attacks.
Other vulnerabilities in Gravity Forms plugin for WordPress
See all- CVE-2026-5113High
The Gravity Forms plugin for WordPress is vulnerable to Stored Cross-Site Scripting (XSS) via Consent field hidden inputs in versions up to 2.10.0. The issue arises from a flawed state validation mechanism that improperly sanitizes input.
- CVE-2026-5112High
The Gravity Forms plugin for WordPress is vulnerable to Unauthenticated Stored Cross-Site Scripting in versions up to 2.10.0. The issue arises from insufficient input validation and output escaping of product names in Repeater fields.
- CVE-2026-5110High
The Gravity Forms plugin for WordPress is vulnerable to Unauthenticated Stored Cross-Site Scripting in versions up to 2.10.0. This is due to insufficient input validation and output escaping in the SingleProduct field when used inside a Repeater field.
- CVE-2026-5109High
The Gravity Forms plugin for WordPress is vulnerable to Stored Cross-Site Scripting in versions up to and including 2.10.0. This is due to insufficient validation and output escaping of Product Option field values, allowing raw unsanitized data to be stored in the database.
Original NVD description (English source)
The Gravity Forms plugin for WordPress is vulnerable to Stored Cross-Site Scripting in versions up to and including 2.10.0. This is due to insufficient input validation and output escaping on Hidden Product field values when used inside Repeater fields, where repeater subfields bypass state validation checks and the Hidden Product validate() method only validates the quantity field while ignoring the product name field that is later output without proper escaping in the get_value_entry_detail() method. This makes it possible for unauthenticated attackers to inject arbitrary web scripts through form submissions that will execute whenever an administrator views the entry details.