<?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>HT Contact Form – Drag &amp; Drop Form Builder for WordPress Plugin &lt;= 2.8.2 — CraftedSignal Threat Feed</title><link>https://feed.craftedsignal.io/products/ht-contact-form--drag--drop-form-builder-for-wordpress-plugin--2.8.2/</link><description>Trending threats, MITRE ATT&amp;CK coverage, and detection metadata. Fed continuously.</description><generator>Hugo</generator><language>en</language><managingEditor>hello@craftedsignal.io</managingEditor><webMaster>hello@craftedsignal.io</webMaster><lastBuildDate>Thu, 28 May 2026 08:18:59 +0000</lastBuildDate><atom:link href="https://feed.craftedsignal.io/products/ht-contact-form--drag--drop-form-builder-for-wordpress-plugin--2.8.2/feed.xml" rel="self" type="application/rss+xml"/><item><title>HT Contact Form WordPress Plugin Vulnerable to Stored XSS (CVE-2026-7052)</title><link>https://feed.craftedsignal.io/briefs/2026-05-wordpress-ht-contact-form-xss/</link><pubDate>Thu, 28 May 2026 08:18:59 +0000</pubDate><author>hello@craftedsignal.io</author><guid isPermaLink="true">https://feed.craftedsignal.io/briefs/2026-05-wordpress-ht-contact-form-xss/</guid><description>The HT Contact Form – Drag &amp; Drop Form Builder for WordPress plugin for WordPress is vulnerable to Stored Cross-Site Scripting (CVE-2026-7052) via the 'file_upload' parameter in versions up to 2.8.2, allowing unauthenticated attackers to inject arbitrary web scripts.</description><content:encoded><![CDATA[<p>The HT Contact Form – Drag &amp; Drop Form Builder for WordPress plugin, a popular tool for creating contact forms on WordPress websites, is susceptible to a Stored Cross-Site Scripting (XSS) vulnerability. Identified as CVE-2026-7052, this flaw affects all versions up to and including 2.8.2. The vulnerability lies within the &lsquo;file_upload&rsquo; parameter, where insufficient input sanitization and output escaping allow unauthenticated attackers to inject arbitrary web scripts. Successful exploitation requires the &lsquo;Store Submissions&rsquo; setting to be enabled in the plugin, as this setting determines whether unsanitized field values are persisted to the database. These persisted values are then rendered without proper escaping in the admin entry viewer, leading to XSS when an administrator views the submission. This poses a significant risk to WordPress sites using the vulnerable plugin, as malicious scripts can compromise administrator accounts and potentially the entire website.</p>
<h2 id="attack-chain">Attack Chain</h2>
<ol>
<li>An unauthenticated attacker crafts a malicious HTTP POST request to a WordPress page containing a HT Contact Form.</li>
<li>The attacker injects a JavaScript payload into the &lsquo;file_upload&rsquo; parameter of the form.</li>
<li>The vulnerable HT Contact Form plugin processes the form submission without proper sanitization or output encoding of the &lsquo;file_upload&rsquo; parameter.</li>
<li>If the &lsquo;Store Submissions&rsquo; setting is enabled, the malicious payload is stored in the WordPress database.</li>
<li>An administrator logs into the WordPress admin panel.</li>
<li>The administrator navigates to the HT Contact Form submissions page, triggering the rendering of the stored, unsanitized &lsquo;file_upload&rsquo; value.</li>
<li>The injected JavaScript payload executes within the administrator&rsquo;s browser session.</li>
<li>The attacker gains control of the administrator&rsquo;s session, potentially leading to further compromise of the WordPress website, such as plugin modification or arbitrary code execution.</li>
</ol>
<h2 id="impact">Impact</h2>
<p>Successful exploitation of this Stored XSS vulnerability (CVE-2026-7052) can lead to a complete compromise of the affected WordPress website. An attacker can inject malicious JavaScript code that executes within the administrator&rsquo;s browser, allowing them to steal credentials, modify website content, install malicious plugins, or redirect users to phishing sites. Given the popularity of the HT Contact Form plugin, a large number of WordPress websites are potentially vulnerable. The impact is magnified when considering that administrators typically have extensive privileges, enabling attackers to perform privileged actions.</p>
<h2 id="recommendation">Recommendation</h2>
<ul>
<li>Upgrade the HT Contact Form – Drag &amp; Drop Form Builder for WordPress plugin to the latest version (greater than 2.8.2) to patch CVE-2026-7052.</li>
<li>Deploy the provided Sigma rule to detect attempts to inject malicious JavaScript code into the <code>file_upload</code> parameter within HTTP POST requests targeting WordPress pages with contact forms.</li>
<li>Enable input validation and output encoding on all user-supplied data, especially for form fields, to prevent XSS vulnerabilities.</li>
<li>If upgrading is not immediately possible, disable the &lsquo;Store Submissions&rsquo; setting within the HT Contact Form plugin as a temporary mitigation, albeit with reduced functionality.</li>
</ul>
]]></content:encoded><category domain="severity">medium</category><category domain="type">advisory</category><category>stored-xss</category><category>wordpress</category><category>plugin</category><category>CVE-2026-7052</category></item></channel></rss>