<?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/" xmlns:webfeeds="http://webfeeds.org/rss/1.0"><channel><title>WPForms Pro - CraftedSignal Threat Feed</title><link>https://feed.craftedsignal.io/products/wpforms-pro/</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>Fri, 21 Aug 2026 05:22:11 +0000</lastBuildDate><atom:link href="https://feed.craftedsignal.io/products/wpforms-pro/feed.xml" rel="self" type="application/rss+xml"/><image><url>https://feed.craftedsignal.io/favicon-32x32.png</url><title>CraftedSignal Threat Feed</title><link>https://feed.craftedsignal.io/</link><width>32</width><height>32</height></image><webfeeds:icon>https://feed.craftedsignal.io/favicon.svg</webfeeds:icon><item><title>Stored XSS in WPForms Pro Plugin</title><link>https://feed.craftedsignal.io/briefs/2026-08-wpforms-xss/</link><pubDate>Fri, 21 Aug 2026 05:22:11 +0000</pubDate><author>hello@craftedsignal.io</author><guid isPermaLink="true">https://feed.craftedsignal.io/briefs/2026-08-wpforms-xss/</guid><description>WPForms Pro versions up to 2.0.0.2 are vulnerable to unauthenticated Stored Cross-Site Scripting via improper input sanitization in text fields.</description><content:encoded><![CDATA[<p>WPForms Pro, a widely used WordPress form-building plugin, contains a critical Stored Cross-Site Scripting (XSS) vulnerability in versions 2.0.0.2 and earlier. The flaw exists due to insufficient input sanitization and output escaping within the Single Line Text and Paragraph Text fields. An unauthenticated attacker can exploit this by submitting specially crafted input containing iframe elements.</p>
<p>The vulnerability is specifically enabled by the plugin's modification of the <code>wp_kses_allowed_html</code> filter. This modification widens the allowlist to permit <code>iframe</code> elements with a <code>data-src</code> attribute. Since <code>data-src</code> is not subject to standard WordPress URI-attribute sanitization, an attacker can store a <code>javascript:</code> URI. When a site administrator views the entry via the bundled <code>view-entry.min.js</code> script, the application promotes the <code>data-src</code> attribute to a live <code>src</code> attribute, resulting in the execution of arbitrary JavaScript in the context of the administrator's session.</p>
<h2 id="impact">Impact</h2>
<p>Successful exploitation allows an unauthenticated attacker to inject malicious scripts into WordPress site entries. When an administrator views these entries, the script executes, potentially leading to unauthorized administrative actions, account takeover, or the exfiltration of sensitive site data. Given the ubiquity of form plugins, this affects a broad range of WordPress-powered websites.</p>
<h2 id="recommendation">Recommendation</h2>
<ul>
<li>Update WPForms Pro to a version beyond 2.0.0.2 immediately to receive the corrected sanitization logic.</li>
<li>Review administrative access logs for unusual patterns or activity originating from the plugin's entry view interface.</li>
<li>Audit existing form entries for anomalous iframe or script tags if the plugin cannot be updated immediately.</li>
</ul>
]]></content:encoded><category domain="severity">high</category><category domain="type">advisory</category></item></channel></rss>