CVE-2026-5112
HighSummary
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.
Risk Assessment
Attackers can inject malicious HTML scripts, potentially leading to user data theft or session hijacking. This poses a significant security risk to the application and user data.
Recommendation
It is recommended to update the Gravity Forms plugin to the latest version to mitigate this vulnerability. Additionally, implementing further input validation and data sanitization mechanisms is advisable.
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-5111High
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.
- 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 Unauthenticated Stored Cross-Site Scripting in versions up to and including 2.10.0. This is due to insufficient input validation and output escaping of Calculation Product field product names when rendered inside Repeater fields. The validate() method in the GF_Field_Calculation class only validates the quantity field (.3) and completely ignores the product name field (.1), allowing malicious HTML to pass through validation. When the value is saved, the sanitize_entry_value() method returns the raw value without sanitization for fields where HTML is not expected. Subsequently, when an entry is viewed in wp-admin, the get_value_entry_detail() method concatenates the unescaped product name directly into the output string, which is then rendered by the repeater's get_value_entry_detail() method without further escaping. This makes it possible for unauthenticated attackers to inject arbitrary web scripts via form submissions that will