<?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>Woocommerce — CraftedSignal Threat Feed</title><link>https://feed.craftedsignal.io/tags/woocommerce/</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 14:16:17 +0000</lastBuildDate><atom:link href="https://feed.craftedsignal.io/tags/woocommerce/feed.xml" rel="self" type="application/rss+xml"/><item><title>WordPress WCFM Plugin Vulnerable to IDOR Leading to Account Deletion</title><link>https://feed.craftedsignal.io/briefs/2026-05-wordpress-wcfm-idor/</link><pubDate>Sat, 02 May 2026 14:16:17 +0000</pubDate><author>hello@craftedsignal.io</author><guid isPermaLink="true">https://feed.craftedsignal.io/briefs/2026-05-wordpress-wcfm-idor/</guid><description>The WCFM plugin for WordPress is vulnerable to an Insecure Direct Object Reference (IDOR) that allows authenticated attackers with Vendor-level access or higher to delete arbitrary users, including administrators.</description><content:encoded><![CDATA[<p>The WCFM – Frontend Manager for WooCommerce along with Bookings Subscription Listings Compatible plugin, a popular WordPress plugin, is affected by an Insecure Direct Object Reference (IDOR) vulnerability. This flaw, present in versions up to and including 6.7.25, stems from a lack of proper validation on the <code>customerid</code> parameter within the <code>wcfm_delete_wcfm_customer</code> function. An attacker with Vendor-level privileges or higher can exploit this vulnerability to delete any user account on the WordPress instance, including those with administrative rights. This can lead to complete compromise of the affected website.</p>
<h2 id="attack-chain">Attack Chain</h2>
<ol>
<li>An attacker authenticates to the WordPress site with Vendor-level access or higher.</li>
<li>The attacker crafts a malicious HTTP request targeting the <code>wcfm_delete_wcfm_customer</code> function.</li>
<li>The attacker includes the <code>customerid</code> parameter in the request, setting its value to the ID of the target user account they wish to delete.</li>
<li>Due to the missing validation on the <code>customerid</code> parameter, the application directly uses the provided ID to locate the user account.</li>
<li>The <code>wcfm_delete_wcfm_customer</code> function proceeds to delete the user account identified by the attacker-supplied <code>customerid</code>.</li>
<li>The targeted user account is successfully deleted from the WordPress instance.</li>
<li>If the deleted user account was an administrator, the attacker can effectively take control of the website.</li>
</ol>
<h2 id="impact">Impact</h2>
<p>Successful exploitation of this IDOR vulnerability allows an attacker to delete arbitrary user accounts, including those with administrative privileges. This can lead to a complete compromise of the affected WordPress website. An attacker could then deface the website, steal sensitive data, or use it to launch further attacks. Due to the popularity of the plugin, a large number of WooCommerce stores are potentially affected.</p>
<h2 id="recommendation">Recommendation</h2>
<ul>
<li>Apply the latest available patch or upgrade to a version of the WCFM plugin greater than 6.7.25 to remediate CVE-2026-2554.</li>
<li>Monitor web server logs for suspicious requests to <code>wcfm_delete_wcfm_customer</code> with unusual <code>customerid</code> values, using the Sigma rule provided below.</li>
<li>Implement input validation on the <code>customerid</code> parameter within the <code>wcfm_delete_wcfm_customer</code> function to prevent arbitrary user deletion.</li>
</ul>
]]></content:encoded><category domain="severity">high</category><category domain="type">advisory</category><category>idor</category><category>wordpress</category><category>woocommerce</category><category>account-deletion</category></item><item><title>WooCommerce Ajax Product Filter Plugin Vulnerable to SQL Injection (CVE-2026-3396)</title><link>https://feed.craftedsignal.io/briefs/2026-04-woocommerce-sqli/</link><pubDate>Wed, 08 Apr 2026 12:16:21 +0000</pubDate><author>hello@craftedsignal.io</author><guid isPermaLink="true">https://feed.craftedsignal.io/briefs/2026-04-woocommerce-sqli/</guid><description>The WCAPF - WooCommerce Ajax Product Filter plugin is vulnerable to time-based SQL Injection (CVE-2026-3396) due to insufficient escaping and SQL query preparation, allowing unauthenticated attackers to extract sensitive information from the database in versions up to 4.2.3.</description><content:encoded><![CDATA[<p>The WooCommerce Ajax Product Filter (WCAPF) plugin, a WordPress extension, is susceptible to a time-based SQL Injection vulnerability (CVE-2026-3396). This flaw stems from inadequate input sanitization of the <code>post-author</code> parameter and insufficient preparation within the existing SQL query structure. Specifically, all versions of the plugin up to and including version 4.2.3 are affected. An unauthenticated attacker can exploit this vulnerability by injecting malicious SQL code into the <code>post-author</code> parameter. Successful exploitation allows the attacker to manipulate database queries and extract sensitive information without requiring authentication. This vulnerability poses a significant risk to e-commerce sites using the WCAPF plugin, as attackers could potentially access customer data, administrative credentials, or other confidential information.</p>
<h2 id="attack-chain">Attack Chain</h2>
<ol>
<li>An unauthenticated attacker identifies a WooCommerce website using a vulnerable version (&lt;=4.2.3) of the WCAPF plugin.</li>
<li>The attacker crafts a malicious HTTP request targeting an endpoint that utilizes the vulnerable <code>post-author</code> parameter.</li>
<li>The crafted request includes SQL injection payload within the <code>post-author</code> parameter, designed to extract data using time-based techniques. For example, the attacker might use a <code>SLEEP()</code> function to introduce delays based on conditional database queries.</li>
<li>The web server processes the request and passes the unsanitized <code>post-author</code> parameter to the database query.</li>
<li>The injected SQL code manipulates the original query, causing the database to execute the attacker&rsquo;s malicious commands.</li>
<li>Based on the response time (due to the <code>SLEEP()</code> function), the attacker infers whether their injected SQL query was successful in retrieving specific data.</li>
<li>The attacker iteratively refines their SQL injection payload to extract sensitive information, such as user credentials or customer details.</li>
<li>The attacker exfiltrates the obtained data, potentially using it for identity theft, financial fraud, or further attacks against the compromised website.</li>
</ol>
<h2 id="impact">Impact</h2>
<p>Successful exploitation of CVE-2026-3396 can lead to the complete compromise of the vulnerable WooCommerce website&rsquo;s database. An attacker could potentially access sensitive customer data, including names, addresses, credit card details, and purchase history. Furthermore, administrative credentials could be stolen, allowing the attacker to gain full control over the website. This can result in significant financial losses, reputational damage, and legal liabilities for the affected e-commerce business. While the exact number of affected websites is unknown, any online store using the WCAPF plugin versions 4.2.3 or earlier is potentially at risk.</p>
<h2 id="recommendation">Recommendation</h2>
<ul>
<li>Upgrade the WCAPF plugin to a version greater than 4.2.3 to patch CVE-2026-3396 (references: CVE-2026-3396).</li>
<li>Deploy the Sigma rule <code>Detect WooCommerce SQL Injection Attempt</code> to identify potential exploitation attempts in web server logs (references: Sigma rule).</li>
<li>Implement input validation and sanitization on the <code>post-author</code> parameter to prevent SQL injection attacks (references: Attack Chain).</li>
<li>Monitor web server logs for suspicious requests containing SQL injection payloads, particularly those targeting WCAPF plugin endpoints (references: Sigma rule, Attack Chain).</li>
</ul>
]]></content:encoded><category domain="severity">high</category><category domain="type">advisory</category><category>woocommerce</category><category>sqli</category><category>cve-2026-3396</category><category>wordpress</category><category>plugin</category></item><item><title>Product Feed PRO for WooCommerce Plugin CSRF Vulnerability (CVE-2026-3499)</title><link>https://feed.craftedsignal.io/briefs/2026-04-woocommerce-csrf/</link><pubDate>Wed, 08 Apr 2026 02:16:04 +0000</pubDate><author>hello@craftedsignal.io</author><guid isPermaLink="true">https://feed.craftedsignal.io/briefs/2026-04-woocommerce-csrf/</guid><description>The Product Feed PRO for WooCommerce WordPress plugin (versions 13.4.6-13.5.2.1) is vulnerable to Cross-Site Request Forgery (CSRF) attacks, allowing unauthenticated attackers to perform administrative actions by tricking an administrator into clicking a malicious link.</description><content:encoded><![CDATA[<p>The Product Feed PRO for WooCommerce by AdTribes – Product Feeds for WooCommerce plugin, a WordPress plugin, suffers from a Cross-Site Request Forgery (CSRF) vulnerability. Present in versions 13.4.6 through 13.5.2.1, this flaw allows unauthenticated attackers to execute administrative functions if they can successfully coerce a site administrator into performing an action, such as clicking a specially crafted link. The vulnerability stems from the plugin&rsquo;s failure to implement proper nonce validation on several AJAX actions, including <code>ajax_migrate_to_custom_post_type</code>, <code>ajax_adt_clear_custom_attributes_product_meta_keys</code>, <code>ajax_update_file_url_to_lower_case</code>, <code>ajax_use_legacy_filters_and_rules</code>, and <code>ajax_fix_duplicate_feed</code>. This vulnerability poses a significant risk to WooCommerce store owners using the affected plugin.</p>
<h2 id="attack-chain">Attack Chain</h2>
<ol>
<li>The attacker crafts a malicious URL containing a request to one of the vulnerable AJAX actions (e.g., <code>ajax_migrate_to_custom_post_type</code>).</li>
<li>The attacker distributes the malicious URL via email, social media, or another channel, attempting to trick a WordPress administrator into clicking the link.</li>
<li>The administrator, while authenticated to the WordPress admin panel, clicks the malicious link.</li>
<li>The administrator&rsquo;s browser sends the forged request to the WordPress server, including the administrator&rsquo;s session cookies.</li>
<li>Due to the missing or incorrect nonce validation, the WordPress server processes the request as if it were a legitimate action performed by the administrator.</li>
<li>Depending on the specific AJAX action targeted, the attacker can trigger feed migration, clear custom attribute caches, rewrite feed file URLs to lowercase, toggle legacy filter and rule settings, or delete duplicate feed posts.</li>
<li>The attacker repeats this process to perform other administrative actions, gaining control over the plugin&rsquo;s settings and data.</li>
<li>The attacker potentially manipulates product feeds to inject malicious content, redirect users, or compromise the WooCommerce store&rsquo;s SEO.</li>
</ol>
<h2 id="impact">Impact</h2>
<p>Successful exploitation of this CSRF vulnerability (CVE-2026-3499) could allow an attacker to manipulate a WooCommerce store&rsquo;s product feeds, potentially leading to data corruption, SEO poisoning, or the injection of malicious content. If successful, attackers could modify product information, redirect users to phishing sites, or damage the store&rsquo;s reputation. The severity of the impact depends on the targeted AJAX action, but the potential for unauthorized administrative control is significant. Given the wide usage of WooCommerce and the Product Feed PRO plugin, a large number of online stores are potentially at risk.</p>
<h2 id="recommendation">Recommendation</h2>
<ul>
<li>Upgrade the Product Feed PRO for WooCommerce plugin to a patched version greater than 13.5.2.1 to remediate CVE-2026-3499.</li>
<li>Deploy the provided Sigma rules to your SIEM to detect exploitation attempts targeting the vulnerable AJAX actions.</li>
<li>Implement web application firewall (WAF) rules to block requests to the vulnerable AJAX endpoints originating from suspicious referrers.</li>
<li>Educate WordPress administrators on the risks of CSRF attacks and the importance of verifying links before clicking them.</li>
</ul>
]]></content:encoded><category domain="severity">high</category><category domain="type">advisory</category><category>wordpress</category><category>woocommerce</category><category>csrf</category><category>cve-2026-3499</category></item><item><title>ReviewX WordPress Plugin Arbitrary Method Call Vulnerability</title><link>https://feed.craftedsignal.io/briefs/2026-03-reviewx-rce/</link><pubDate>Tue, 24 Mar 2026 12:00:00 +0000</pubDate><author>hello@craftedsignal.io</author><guid isPermaLink="true">https://feed.craftedsignal.io/briefs/2026-03-reviewx-rce/</guid><description>The ReviewX WordPress plugin is vulnerable to arbitrary method calls, allowing unauthenticated attackers to potentially achieve remote code execution.</description><content:encoded><![CDATA[<p>The ReviewX – WooCommerce Product Reviews plugin for WordPress, a tool designed to enhance product reviews, contains a critical vulnerability. Identified as CVE-2025-10679, this flaw stems from insufficient input validation within the <code>bulkTenReviews</code> function. Exploitation allows unauthenticated attackers to invoke arbitrary PHP class methods that either require no input or can utilize default values. This vulnerability affects ReviewX plugin versions up to and including 2.2.12. Successful exploitation can lead to sensitive information disclosure or, under certain server configurations and available methods, remote code execution. This poses a significant risk to e-commerce sites utilizing the vulnerable plugin, potentially impacting customer data and overall site integrity.</p>
<h2 id="attack-chain">Attack Chain</h2>
<ol>
<li>The attacker sends a crafted HTTP request to the WordPress server targeting the vulnerable <code>bulkTenReviews</code> function in the ReviewX plugin.</li>
<li>The crafted request includes malicious input designed to bypass the insufficient input validation within the <code>bulkTenReviews</code> function.</li>
<li>The <code>bulkTenReviews</code> function processes the attacker-controlled data without proper sanitization.</li>
<li>The unsanitized input is passed to a variable function call mechanism, allowing the attacker to specify an arbitrary PHP class method.</li>
<li>The attacker leverages this vulnerability to call a PHP class method that requires no inputs or has default values.</li>
<li>Depending on the available methods and server configuration, the attacker may be able to trigger sensitive information disclosure.</li>
<li>In more critical scenarios, the attacker might be able to call methods that allow writing to the file system or executing arbitrary commands, leading to remote code execution.</li>
<li>The attacker gains control of the WordPress server, enabling them to install malware, steal data, or deface the website.</li>
</ol>
<h2 id="impact">Impact</h2>
<p>Successful exploitation of CVE-2025-10679 can lead to a range of damaging consequences. Sensitive information, such as customer data and administrative credentials, may be exposed. In the worst-case scenario, attackers can achieve remote code execution, granting them complete control over the affected WordPress server. This can result in website defacement, data theft, malware installation, and denial-of-service attacks. Given the wide usage of WooCommerce and ReviewX, a successful widespread attack could impact numerous e-commerce businesses.</p>
<h2 id="recommendation">Recommendation</h2>
<ul>
<li>Immediately update the ReviewX plugin to the latest version (greater than 2.2.12) to patch CVE-2025-10679.</li>
<li>Deploy the Sigma rule <code>Detect ReviewX Arbitrary Method Calls</code> to detect exploitation attempts targeting the <code>bulkTenReviews</code> function.</li>
<li>Monitor web server logs for suspicious POST requests to WordPress plugins with unusual parameters, as highlighted in the Sigma rule <code>Detect ReviewX Arbitrary Method Calls</code>.</li>
<li>Review PHP configurations to harden against potential RCE attempts stemming from arbitrary method calls.</li>
</ul>
]]></content:encoded><category domain="severity">critical</category><category domain="type">advisory</category><category>wordpress</category><category>woocommerce</category><category>reviewx</category><category>rce</category><category>vulnerability</category></item></channel></rss>