<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/"><channel><title>Gravity Forms Plugin &lt;= 2.10.0 — CraftedSignal Threat Feed</title><link>https://feed.craftedsignal.io/products/gravity-forms-plugin--2.10.0/</link><description>Trending threats, MITRE ATT&amp;CK coverage, and detection metadata — refreshed continuously.</description><generator>Hugo</generator><language>en</language><managingEditor>hello@craftedsignal.io</managingEditor><webMaster>hello@craftedsignal.io</webMaster><lastBuildDate>Sat, 02 May 2026 06:16:04 +0000</lastBuildDate><atom:link href="https://feed.craftedsignal.io/products/gravity-forms-plugin--2.10.0/feed.xml" rel="self" type="application/rss+xml"/><item><title>Gravity Forms Plugin Stored XSS Vulnerability (CVE-2026-5113)</title><link>https://feed.craftedsignal.io/briefs/2026-05-gravityforms-xss/</link><pubDate>Sat, 02 May 2026 06:16:04 +0000</pubDate><author>hello@craftedsignal.io</author><guid isPermaLink="true">https://feed.craftedsignal.io/briefs/2026-05-gravityforms-xss/</guid><description>The Gravity Forms plugin for WordPress is vulnerable to stored cross-site scripting (XSS) via Consent field hidden inputs, allowing unauthenticated attackers to inject arbitrary web scripts that execute when an administrator views the entries list page.</description><content:encoded><![CDATA[<p>The Gravity Forms plugin for WordPress, a popular form builder, contains a stored cross-site scripting (XSS) vulnerability identified as CVE-2026-5113. This flaw affects versions up to and including 2.10.0. The vulnerability stems from a flawed state validation mechanism combined with insufficient output escaping within the Consent field&rsquo;s hidden inputs. An unauthenticated attacker can exploit this by injecting malicious JavaScript code into form entries. This malicious code is then executed when an authenticated administrator accesses the Entries List page within the WordPress administration panel, potentially leading to account compromise or other malicious actions performed within the administrator&rsquo;s session. Successful exploitation allows attackers to execute arbitrary web scripts in the context of an administrator&rsquo;s browser.</p>
<h2 id="attack-chain">Attack Chain</h2>
<ol>
<li>An unauthenticated attacker crafts a malicious payload containing XSS code within a Gravity Forms Consent field. The payload leverages HTML tags like <code>&lt;svg&gt;</code> that <code>wp_kses()</code> will strip.</li>
<li>The attacker submits the crafted form entry to the WordPress site.</li>
<li>The Gravity Forms plugin&rsquo;s state validation mechanism calculates two hashes: one for the raw input and another after sanitization via <code>wp_kses()</code>.</li>
<li>Due to the nature of the XSS payload, the <code>wp_kses()</code> function strips the <code>&lt;svg&gt;</code> tag, resulting in a matching hash for the sanitized input.</li>
<li>The flawed validation logic fails to detect the malicious intent because at least one hash matches the original state, allowing the malicious raw value (containing the XSS payload) to be stored in the database.</li>
<li>An authenticated administrator logs into the WordPress administration panel.</li>
<li>The administrator navigates to the Entries List page for the affected Gravity Form.</li>
<li>The stored malicious consent label is retrieved from the database and output without proper escaping, causing the XSS payload to execute within the administrator&rsquo;s browser session.</li>
</ol>
<h2 id="impact">Impact</h2>
<p>Successful exploitation of CVE-2026-5113 allows unauthenticated attackers to execute arbitrary web scripts within the context of an authenticated administrator&rsquo;s browser session. This can lead to a variety of malicious outcomes, including account compromise, data theft, modification of website content, or further propagation of the attack to other administrative users. The severity of the impact depends on the privileges held by the compromised administrator account.</p>
<h2 id="recommendation">Recommendation</h2>
<ul>
<li>Upgrade the Gravity Forms plugin to the latest version, which includes a fix for CVE-2026-5113.</li>
<li>Implement a Web Application Firewall (WAF) rule to filter out requests containing potentially malicious XSS payloads targeting the Gravity Forms Consent field.</li>
<li>Monitor web server logs for suspicious activity related to form submissions containing encoded or obfuscated JavaScript code. Analyze HTTP request parameters for unusual characters or patterns indicative of XSS attempts.</li>
<li>Enable output escaping on form entries to prevent stored XSS attacks.</li>
</ul>
]]></content:encoded><category domain="severity">medium</category><category domain="type">advisory</category><category>xss</category><category>wordpress</category><category>gravityforms</category><category>cve-2026-5113</category><category>stored-xss</category></item><item><title>Gravity Forms Plugin Unauthenticated Stored XSS Vulnerability</title><link>https://feed.craftedsignal.io/briefs/2024-01-gravity-forms-xss/</link><pubDate>Wed, 03 Jan 2024 12:00:00 +0000</pubDate><author>hello@craftedsignal.io</author><guid isPermaLink="true">https://feed.craftedsignal.io/briefs/2024-01-gravity-forms-xss/</guid><description>The Gravity Forms plugin for WordPress is vulnerable to unauthenticated stored cross-site scripting (XSS) in versions up to 2.10.0, allowing attackers to inject arbitrary JavaScript code into the product name field within repeater fields, which executes when an administrator views the affected entry.</description><content:encoded><![CDATA[<p>The Gravity Forms plugin, a widely used WordPress plugin, is susceptible to an unauthenticated stored cross-site scripting (XSS) vulnerability. This flaw, identified as CVE-2026-5110, affects versions up to and including 2.10.0. The vulnerability stems from inadequate input validation and output escaping specifically within the SingleProduct field when it is nested inside a Repeater field. This bypasses normal state validation, allowing attackers to inject malicious HTML and JavaScript into the product name field. The injected payload is then stored unsanitized in the database. This vulnerability allows unauthenticated attackers to inject arbitrary web scripts that execute whenever an administrator accesses an entry containing the malicious payload through the WordPress admin interface.</p>
<h2 id="attack-chain">Attack Chain</h2>
<ol>
<li>An unauthenticated attacker crafts a malicious request to a WordPress endpoint utilizing the Gravity Forms plugin.</li>
<li>The attacker injects arbitrary HTML and JavaScript into the &lsquo;product name&rsquo; field (input .1) of a SingleProduct field nested within a Repeater field.</li>
<li>Due to insufficient validation within the <code>validate_subfield()</code> method, the malicious input bypasses the state validation mechanism <code>(failed_state_validation())</code>.</li>
<li>The <code>sanitize_entry_value()</code> method returns the raw, unsanitized value because HTML is not expected for the affected field type.</li>
<li>The malicious input is stored in the WordPress database without proper sanitization or escaping.</li>
<li>An administrator accesses the Gravity Forms entries page in the WordPress admin interface (wp-admin/admin.php?page=gf_entries).</li>
<li>The <code>get_value_entry_detail()</code> method retrieves the malicious product name from the database and outputs it without proper escaping.</li>
<li>The stored XSS payload executes in the administrator&rsquo;s browser, potentially allowing the attacker to perform actions with the administrator&rsquo;s privileges.</li>
</ol>
<h2 id="impact">Impact</h2>
<p>Successful exploitation of this vulnerability allows an unauthenticated attacker to execute arbitrary JavaScript code in the context of an administrator&rsquo;s browser session. This can lead to account compromise, data theft, or further malicious activities within the WordPress administration panel. The vulnerability affects all users of the Gravity Forms plugin on WordPress installations with versions up to and including 2.10.0.</p>
<h2 id="recommendation">Recommendation</h2>
<ul>
<li>Upgrade the Gravity Forms plugin to the latest version (greater than 2.10.0) to patch CVE-2026-5110.</li>
<li>Deploy the provided Sigma rule <code>Detect Gravity Forms XSS Attempt</code> to identify potential exploitation attempts by monitoring for specific patterns in HTTP requests.</li>
<li>Enable web server logging to capture detailed information about HTTP requests and responses, enabling the Sigma rule&rsquo;s effectiveness.</li>
</ul>
]]></content:encoded><category domain="severity">medium</category><category domain="type">advisory</category><category>xss</category><category>wordpress</category><category>gravityforms</category></item></channel></rss>