<?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>Query Shortcode Plugin &lt;= 0.2.1 — CraftedSignal Threat Feed</title><link>https://feed.craftedsignal.io/products/query-shortcode-plugin--0.2.1/</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, 27 May 2026 07:18:42 +0000</lastBuildDate><atom:link href="https://feed.craftedsignal.io/products/query-shortcode-plugin--0.2.1/feed.xml" rel="self" type="application/rss+xml"/><item><title>CVE-2026-9200: WordPress Query Shortcode Plugin Vulnerable to Local File Inclusion</title><link>https://feed.craftedsignal.io/briefs/2026-05-cve-2026-9200-wordpress-lfi/</link><pubDate>Wed, 27 May 2026 07:18:42 +0000</pubDate><author>hello@craftedsignal.io</author><guid isPermaLink="true">https://feed.craftedsignal.io/briefs/2026-05-cve-2026-9200-wordpress-lfi/</guid><description>The Query Shortcode plugin for WordPress is vulnerable to Local File Inclusion (CVE-2026-9200) in versions up to 0.2.1, allowing authenticated attackers with contributor-level access and above to include and execute arbitrary PHP files on the server, potentially leading to privilege escalation and code execution.</description><content:encoded><![CDATA[<p>The Query Shortcode plugin for WordPress, in versions up to and including 0.2.1, is susceptible to a Local File Inclusion (LFI) vulnerability, tracked as CVE-2026-9200. This vulnerability allows authenticated attackers with contributor-level access or higher to inject malicious code through the shortcode functionality. By exploiting this flaw, attackers can include and execute arbitrary PHP files residing on the server. This can be leveraged to bypass existing access controls, potentially exposing sensitive data or allowing the execution of arbitrary PHP code, leading to complete system compromise. The vulnerability stems from insufficient input validation within the shortcode processing mechanism of the plugin.</p>
<h2 id="attack-chain">Attack Chain</h2>
<ol>
<li>Attacker gains contributor-level access or higher to the WordPress site.</li>
<li>Attacker crafts a malicious shortcode containing a path to a PHP file they wish to include.</li>
<li>Attacker injects the malicious shortcode into a WordPress page or post.</li>
<li>WordPress parses the shortcode using the vulnerable Query Shortcode plugin.</li>
<li>The plugin fails to properly sanitize the provided file path.</li>
<li>The plugin includes and executes the specified PHP file from the attacker-controlled path.</li>
<li>The attacker gains arbitrary code execution on the web server.</li>
<li>The attacker escalates privileges and compromises the server.</li>
</ol>
<h2 id="impact">Impact</h2>
<p>Successful exploitation of CVE-2026-9200 allows attackers to execute arbitrary PHP code on the WordPress server. This could lead to a number of detrimental outcomes, including unauthorized access to sensitive data, modification of website content, or complete takeover of the server. This vulnerability affects all WordPress installations utilizing the Query Shortcode plugin version 0.2.1 or earlier. Given the popularity of WordPress and its plugin ecosystem, the potential number of victims is substantial.</p>
<h2 id="recommendation">Recommendation</h2>
<ul>
<li>Immediately upgrade the Query Shortcode plugin to the latest available version to remediate CVE-2026-9200.</li>
<li>Deploy the Sigma rule &ldquo;Detect CVE-2026-9200 Exploitation Attempt via WordPress Query Shortcode&rdquo; to identify potential exploitation attempts.</li>
<li>Review WordPress user roles and permissions to ensure the principle of least privilege is enforced.</li>
<li>Implement web application firewall (WAF) rules to filter out malicious shortcode injections targeting CVE-2026-9200.</li>
</ul>
]]></content:encoded><category domain="severity">high</category><category domain="type">threat</category><category>local-file-inclusion</category><category>wordpress</category><category>plugin-vulnerability</category><category>CVE-2026-9200</category></item></channel></rss>