CVE-2026-5109
HighSummary
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.
Risk Assessment
Unauthenticated attackers can inject arbitrary web scripts into entry data that will execute whenever administrators access the entry details page. This poses a serious security risk to the organization's data.
Recommendation
It is recommended to update the Gravity Forms plugin to the latest version to mitigate this vulnerability. Additionally, conducting a database audit to detect potential script injections 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-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-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.
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 validation and output escaping of Product Option field values. The vulnerability exists because the state validation function accepts submitted values where the wp_kses()-sanitized version matches a legitimate option value, but then stores the raw unsanitized value in the database. When administrators view entry details via the Order Summary section, the option_label is output directly without escaping (view-order-summary.php line 32), executing the injected JavaScript. This makes it possible for unauthenticated attackers to inject arbitrary web scripts in entry data that will execute whenever an administrator accesses the entry details page.