<?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>Javascript-Injection — CraftedSignal Threat Feed</title><link>https://feed.craftedsignal.io/tags/javascript-injection/</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>Tue, 19 May 2026 15:19:24 +0000</lastBuildDate><atom:link href="https://feed.craftedsignal.io/tags/javascript-injection/feed.xml" rel="self" type="application/rss+xml"/><item><title>Funnel Builder for WooCommerce Checkout Missing Authorization Vulnerability (CVE-2026-47100)</title><link>https://feed.craftedsignal.io/briefs/2026-05-funnel-builder-authz-bypass/</link><pubDate>Tue, 19 May 2026 15:19:24 +0000</pubDate><author>hello@craftedsignal.io</author><guid isPermaLink="true">https://feed.craftedsignal.io/briefs/2026-05-funnel-builder-authz-bypass/</guid><description>Funnel Builder for WooCommerce Checkout versions prior to 3.15.0.3 contains a missing authorization vulnerability in the public checkout endpoint that allows unauthenticated attackers to invoke internal methods and inject malicious JavaScript, impacting checkout page visitors.</description><content:encoded><![CDATA[<p>A missing authorization vulnerability exists in the Funnel Builder for WooCommerce Checkout plugin (versions prior to 3.15.0.3). This flaw allows unauthenticated attackers to bypass authorization checks in the public checkout endpoint. By invoking internal methods, attackers can write arbitrary data to the plugin&rsquo;s External Scripts global setting. This injection allows the introduction of malicious JavaScript code. This JavaScript then executes in the browsers of all users visiting the checkout page, potentially leading to credential theft, defacement, or other client-side attacks. The vulnerability was reported on May 19, 2026, and is identified as CVE-2026-47100.</p>
<h2 id="attack-chain">Attack Chain</h2>
<ol>
<li>An unauthenticated attacker identifies the vulnerable checkout endpoint in the Funnel Builder plugin.</li>
<li>The attacker crafts a malicious HTTP request to the checkout endpoint, bypassing authorization checks.</li>
<li>This request invokes an internal method to modify plugin settings.</li>
<li>The attacker writes arbitrary data containing malicious JavaScript code to the External Scripts global setting.</li>
<li>A user visits the checkout page on the affected WooCommerce site.</li>
<li>The injected JavaScript code from the External Scripts setting executes in the user&rsquo;s browser.</li>
<li>The malicious JavaScript performs actions such as stealing payment information, redirecting the user to a phishing site, or defacing the page.</li>
<li>The attacker gains access to sensitive user data or compromises the integrity of the checkout process.</li>
</ol>
<h2 id="impact">Impact</h2>
<p>Successful exploitation of this vulnerability allows an attacker to inject malicious JavaScript into the checkout pages of WooCommerce stores using the Funnel Builder plugin. This could lead to the theft of customer payment information, redirection to phishing sites, or defacement of the checkout page, affecting potentially all users visiting the checkout page. Given the widespread use of WooCommerce for e-commerce, a large number of stores and customers are potentially at risk.</p>
<h2 id="recommendation">Recommendation</h2>
<ul>
<li>Upgrade the Funnel Builder for WooCommerce Checkout plugin to version 3.15.0.3 or later to patch CVE-2026-47100.</li>
<li>Deploy the Sigma rule &ldquo;Detect CVE-2026-47100 Exploitation — Funnel Builder Unauthorized Script Injection&rdquo; to your SIEM to detect exploitation attempts.</li>
<li>Monitor web server logs for suspicious POST requests to checkout endpoints with attempts to modify script settings, as indicated by the log source in the provided Sigma rule.</li>
</ul>
]]></content:encoded><category domain="severity">high</category><category domain="type">threat</category><category>cve</category><category>woocommerce</category><category>wordpress</category><category>missing-authorization</category><category>javascript-injection</category></item></channel></rss>