<?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>CSV Importer 3.3.6 — CraftedSignal Threat Feed</title><link>https://feed.craftedsignal.io/products/csv-importer-3.3.6/</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>Sun, 17 May 2026 13:18:42 +0000</lastBuildDate><atom:link href="https://feed.craftedsignal.io/products/csv-importer-3.3.6/feed.xml" rel="self" type="application/rss+xml"/><item><title>WooCommerce CSV Importer Path Traversal File Deletion (CVE-2018-25325)</title><link>https://feed.craftedsignal.io/briefs/2026-05-woocommerce-path-traversal/</link><pubDate>Sun, 17 May 2026 13:18:42 +0000</pubDate><author>hello@craftedsignal.io</author><guid isPermaLink="true">https://feed.craftedsignal.io/briefs/2026-05-woocommerce-path-traversal/</guid><description>WooCommerce CSV Importer 3.3.6 contains a path traversal vulnerability (CVE-2018-25325) that allows registered users to delete arbitrary files by submitting crafted filenames via the delete_export_file AJAX action.</description><content:encoded><![CDATA[<p>WooCommerce CSV Importer version 3.3.6 is vulnerable to a path traversal vulnerability (CVE-2018-25325). This flaw allows any registered user, even those with low privileges, to delete arbitrary files on the server. The vulnerability is triggered via the <code>delete_export_file</code> AJAX action, where the <code>filename</code> parameter is not properly sanitized. By crafting a POST request with directory traversal sequences (e.g., <code>../</code>), an attacker can bypass intended directory restrictions and delete sensitive files such as <code>wp-config.php</code>. This vulnerability poses a significant risk to WordPress installations using the affected plugin.</p>
<h2 id="attack-chain">Attack Chain</h2>
<ol>
<li>An attacker registers an account on the WordPress site if one does not exist.</li>
<li>The attacker identifies the <code>delete_export_file</code> AJAX action as a target for manipulation.</li>
<li>The attacker crafts a POST request to <code>wp-admin/admin-ajax.php</code> with the action set to <code>delete_export_file</code>.</li>
<li>The POST request includes a <code>filename</code> parameter containing a path traversal sequence, such as <code>../../../../wp-config.php</code>.</li>
<li>The server-side code, lacking proper input validation, processes the request and attempts to delete the file specified by the crafted filename.</li>
<li>Due to the path traversal, the server deletes a file outside of the intended export directory.</li>
<li>If the attacker successfully targets critical files like <code>wp-config.php</code>, the WordPress site may become unstable or inaccessible.</li>
</ol>
<h2 id="impact">Impact</h2>
<p>Successful exploitation of this vulnerability can lead to arbitrary file deletion on the server hosting the WordPress site. An attacker could delete critical configuration files like <code>wp-config.php</code>, rendering the website unusable. The CVSS v3.1 base score for this vulnerability is 7.5, indicating a high severity. While the provided source doesn&rsquo;t list specific victim counts or sectors, the widespread use of WooCommerce makes this vulnerability a significant threat.</p>
<h2 id="recommendation">Recommendation</h2>
<ul>
<li>Upgrade to a patched version of the WooCommerce CSV Importer that addresses the path traversal vulnerability (CVE-2018-25325).</li>
<li>Implement the provided Sigma rule &ldquo;Detect CVE-2018-25325 Exploitation — WooCommerce CSV Importer Path Traversal&rdquo; to detect malicious POST requests attempting to exploit this vulnerability.</li>
<li>Monitor web server logs for POST requests to <code>wp-admin/admin-ajax.php</code> with the <code>delete_export_file</code> action and filenames containing directory traversal sequences (<code>../</code>) to identify potential exploitation attempts.</li>
</ul>
]]></content:encoded><category domain="severity">high</category><category domain="type">advisory</category><category>path-traversal</category><category>file-deletion</category><category>wordpress</category></item></channel></rss>