<?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>RTMKit Addons for Elementor Plugin &lt;= 2.0.2 — CraftedSignal Threat Feed</title><link>https://feed.craftedsignal.io/products/rtmkit-addons-for-elementor-plugin--2.0.2/</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, 13 May 2026 15:51:38 +0000</lastBuildDate><atom:link href="https://feed.craftedsignal.io/products/rtmkit-addons-for-elementor-plugin--2.0.2/feed.xml" rel="self" type="application/rss+xml"/><item><title>RTMKit Addons for Elementor WordPress Plugin LFI Vulnerability (CVE-2026-3425)</title><link>https://feed.craftedsignal.io/briefs/2026-05-rtmkit-lfi/</link><pubDate>Wed, 13 May 2026 15:51:38 +0000</pubDate><author>hello@craftedsignal.io</author><guid isPermaLink="true">https://feed.craftedsignal.io/briefs/2026-05-rtmkit-lfi/</guid><description>The RTMKit Addons for Elementor plugin for WordPress is vulnerable to local file inclusion (LFI) via the 'path' parameter in the 'get_content' AJAX action, allowing authenticated attackers with Author-level access or higher to include and execute arbitrary PHP files, leading to potential code execution.</description><content:encoded><![CDATA[<p>The RTMKit Addons for Elementor plugin, a popular WordPress extension, contains a local file inclusion vulnerability (CVE-2026-3425) affecting versions up to and including 2.0.2. This flaw resides within the &lsquo;get_content&rsquo; AJAX action, specifically through the &lsquo;path&rsquo; parameter. Authenticated users with Author-level privileges or higher can exploit this vulnerability to include and execute arbitrary PHP files residing on the server. This can enable attackers to bypass access controls, obtain sensitive data, or ultimately achieve remote code execution by including uploaded PHP files. This vulnerability poses a significant risk to WordPress websites utilizing the affected plugin.</p>
<h2 id="attack-chain">Attack Chain</h2>
<ol>
<li>An attacker authenticates to the WordPress site with Author-level or higher privileges.</li>
<li>The attacker crafts a malicious HTTP request targeting the &lsquo;admin-ajax.php&rsquo; endpoint.</li>
<li>The request includes the &lsquo;action&rsquo; parameter set to &lsquo;get_content&rsquo;.</li>
<li>The attacker manipulates the &lsquo;path&rsquo; parameter within the request, setting it to point to a sensitive local file or an uploaded PHP file.</li>
<li>The server processes the request and includes the specified file.</li>
<li>If the included file is a PHP file, the server executes the PHP code.</li>
<li>The attacker can leverage this to read sensitive data from the server, such as configuration files.</li>
<li>Alternatively, the attacker could upload a PHP file (e.g., through a separate vulnerability or misconfiguration) and then include it using the LFI vulnerability, achieving arbitrary code execution.</li>
</ol>
<h2 id="impact">Impact</h2>
<p>Successful exploitation of CVE-2026-3425 allows attackers with Author-level access to bypass access controls and execute arbitrary PHP code on the WordPress server. This could lead to the compromise of sensitive data, defacement of the website, or complete takeover of the server. The number of potentially affected websites is significant, given the widespread use of WordPress and the RTMKit Addons for Elementor plugin.</p>
<h2 id="recommendation">Recommendation</h2>
<ul>
<li>Upgrade the RTMKit Addons for Elementor plugin to a version greater than 2.0.2 to patch CVE-2026-3425.</li>
<li>Deploy the Sigma rule &ldquo;Detect CVE-2026-3425 Exploitation — RTMKit LFI Attempt&rdquo; to your SIEM and tune for your environment.</li>
<li>Monitor web server logs for requests to &lsquo;admin-ajax.php&rsquo; with the &lsquo;action&rsquo; parameter set to &lsquo;get_content&rsquo; and suspicious values in the &lsquo;path&rsquo; parameter, using the file paths and extensions in the detection rule as a reference.</li>
</ul>
]]></content:encoded><category domain="severity">high</category><category domain="type">advisory</category><category>lfi</category><category>wordpress</category><category>plugin</category><category>cve-2026-3425</category></item></channel></rss>