<?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>The AI Engine – The Chatbot, AI Framework &amp; MCP for WordPress (3.6.5) - CraftedSignal Threat Feed</title><link>https://feed.craftedsignal.io/products/the-ai-engine--the-chatbot-ai-framework--mcp-for-wordpress-3.6.5/</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>Sat, 01 Aug 2026 09:49:54 +0000</lastBuildDate><atom:link href="https://feed.craftedsignal.io/products/the-ai-engine--the-chatbot-ai-framework--mcp-for-wordpress-3.6.5/feed.xml" rel="self" type="application/rss+xml"/><item><title>CVE-2026-15988: CSRF Vulnerability in AI Engine WordPress Plugin</title><link>https://feed.craftedsignal.io/briefs/2026-08-wp-ai-engine-csrf/</link><pubDate>Sat, 01 Aug 2026 09:49:54 +0000</pubDate><author>hello@craftedsignal.io</author><guid isPermaLink="true">https://feed.craftedsignal.io/briefs/2026-08-wp-ai-engine-csrf/</guid><description>The AI Engine WordPress plugin contains a CSRF vulnerability in the reauth_for_authorize function allowing unauthenticated attackers to create administrator accounts.</description><content:encoded><![CDATA[<p>The AI Engine - The Chatbot, AI Framework &amp; MCP for WordPress plugin is vulnerable to Cross-Site Request Forgery (CSRF) in all versions up to and including 3.6.5. The vulnerability stems from missing or incorrect nonce validation within the <code>reauth_for_authorize</code> function. By leveraging this flaw, an unauthenticated attacker can trick a site administrator into clicking a malicious link, which triggers an unauthorized REST API call. This operation can be combined with WordPress's <code>?_method=POST</code> method-override feature to convert a GET request into an authenticated POST request. The impact of this exploit is severe, as it permits the creation of unauthorized administrator accounts, leading to full site compromise and persistent access for the attacker.</p>
<h2 id="attack-chain">Attack Chain</h2>
<ol>
<li>The attacker crafts a malicious URL targeting a WordPress site running the vulnerable AI Engine plugin.</li>
<li>The attacker delivers the link to a site administrator via social engineering (e.g., phishing).</li>
<li>The administrator, while logged into the WordPress dashboard, clicks the attacker-supplied link.</li>
<li>The browser initiates a request to the <code>reauth_for_authorize</code> endpoint, which fails to validate a nonce.</li>
<li>The attacker utilizes the <code>?_method=POST</code> query parameter to override the HTTP method to POST.</li>
<li>The REST API processes the request as an authenticated administrative action due to the administrator's active session.</li>
<li>The request executes the creation of a new user account with the 'administrator' role using credentials provided by the attacker.</li>
<li>The attacker authenticates as the newly created administrator to gain full control over the WordPress instance.</li>
</ol>
<h2 id="impact">Impact</h2>
<p>Successful exploitation leads to full administrative compromise of the target WordPress site. An attacker gaining administrator-level access can modify site content, redirect traffic, exfiltrate sensitive data, or install further backdoors. The scope of this threat affects any organization utilizing The AI Engine plugin versions 3.6.5 or earlier, posing a significant risk to the integrity and availability of hosted web content.</p>
<h2 id="recommendation">Recommendation</h2>
<p>Prioritize the following actions for your web security teams:</p>
<ul>
<li>Update the AI Engine plugin to version 3.6.6 or higher immediately to apply the vendor-provided security patch.</li>
<li>Audit the WordPress 'Users' table for unauthorized accounts created during the current reporting period.</li>
<li>Deploy web server log monitoring to identify suspicious HTTP POST requests directed toward REST API endpoints containing <code>reauth_for_authorize</code>.</li>
<li>Use the provided Sigma rule to monitor for potential exploitation attempts targeting the vulnerable function.</li>
</ul>
]]></content:encoded><category domain="severity">high</category><category domain="type">advisory</category></item></channel></rss>