<?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>Search Analytics for WP (1.4.16) - CraftedSignal Threat Feed</title><link>https://feed.craftedsignal.io/products/search-analytics-for-wp-1.4.16/</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>Wed, 05 Aug 2026 09:16:52 +0000</lastBuildDate><atom:link href="https://feed.craftedsignal.io/products/search-analytics-for-wp-1.4.16/feed.xml" rel="self" type="application/rss+xml"/><item><title>CSRF Vulnerability in Search Analytics for WP Plugin</title><link>https://feed.craftedsignal.io/briefs/2026-08-search-analytics-wp-csrf/</link><pubDate>Wed, 05 Aug 2026 09:16:52 +0000</pubDate><author>hello@craftedsignal.io</author><guid isPermaLink="true">https://feed.craftedsignal.io/briefs/2026-08-search-analytics-wp-csrf/</guid><description>The Search Analytics for WP plugin for WordPress contains a Cross-Site Request Forgery (CSRF) vulnerability in the process_bulk_action function that allows authenticated administrators to be tricked into deleting arbitrary search-term records.</description><content:encoded><![CDATA[<p>The Search Analytics for WP plugin (versions 1.4.16 and earlier) is vulnerable to a Cross-Site Request Forgery (CSRF) flaw originating from insufficient nonce validation in the MWTSA_Stats_Table class. Specifically, the process_bulk_action function lacks the necessary tokens to verify the legitimacy of a request before performing bulk data operations. This flaw allows an attacker to manipulate an authenticated administrator into executing unauthorized commands. By enticing an administrator to interact with a crafted link or malicious web page while they are logged into the WordPress dashboard, an attacker can trigger the bulk deletion of search-term records and associated history data. This vulnerability is significant for organizations relying on the plugin for audit trails or performance analysis, as the impact involves permanent data loss of sensitive search analytics.</p>
<h2 id="attack-chain">Attack Chain</h2>
<ol>
<li>Attacker identifies the target site running Search Analytics for WP &lt;= 1.4.16.</li>
<li>Attacker crafts a malicious URL or HTML page containing a forged request targeting the plugin's bulk action endpoint.</li>
<li>Attacker uses social engineering to lure an administrator of the WordPress site to visit the malicious resource.</li>
<li>The victim's browser, already holding an active administrator session cookie, automatically executes the request to the target WordPress site.</li>
<li>The WordPress server receives the request and, due to the missing nonce check in process_bulk_action, treats it as a legitimate administrative command.</li>
<li>The plugin logic triggers the deletion of requested search-term records.</li>
<li>The target database is updated, resulting in the loss of search-history rows.</li>
</ol>
<h2 id="impact">Impact</h2>
<p>Successful exploitation results in the unauthorized deletion of arbitrary search-term records and all associated history rows stored in the database. This directly impacts data integrity for WordPress sites using the Search Analytics for WP plugin for data-driven insights. While no direct RCE is reported, the loss of historical data can disrupt business operations and eliminate key audit data regarding user interactions on the site.</p>
<h2 id="recommendation">Recommendation</h2>
<ul>
<li>Update the Search Analytics for WP plugin to version 1.4.17 or higher once the security patch is released by the developer.</li>
<li>Audit web access logs for suspicious administrative activity originating from unexpected referrers that deviate from normal site usage patterns.</li>
<li>Monitor administrative accounts to ensure that they are not using shared or insecure browsing environments while accessing the site backend.</li>
</ul>
]]></content:encoded><category domain="severity">high</category><category domain="type">advisory</category><category>web-application-vulnerability</category><category>wordpress</category><category>csrf</category></item></channel></rss>