CVE-2026-1400 is a vulnerability in the AI Engine – The Chatbot and AI Framework for WordPress plugin, specifically in the rest_helpers_update_media_metadata function. The root cause is the lack of proper file type validation when handling uploads, allowing authenticated users with Editor or higher privileges to upload arbitrary files. The attack vector involves initially uploading a benign image file, which is then renamed to a PHP executable via the update_media_metadata REST API endpoint. This results in an executable PHP file residing in the uploads directory, enabling remote code execution (RCE) on the server hosting the WordPress site. The vulnerability affects all plugin versions up to 3.3.2. The CVSS v3.1 base score is 7.2, reflecting network attack vector, low attack complexity, high privileges required, no user interaction, and high impact on confidentiality, integrity, and availability. The vulnerability is categorized under CWE-434, indicating unrestricted upload of dangerous file types. No official patches have been linked yet, and no known exploits are reported in the wild. However, the vulnerability poses a significant risk due to the common use of WordPress and this plugin in content management and AI chatbot functionalities.

If exploited, this vulnerability allows attackers with Editor-level access to upload and execute arbitrary PHP code on the target server, leading to full server compromise. This can result in unauthorized data access, data modification, defacement of websites, installation of backdoors, and pivoting to other internal systems. The impact extends to confidentiality, integrity, and availability of the affected systems. Given WordPress's widespread use globally, especially in small to medium businesses and content-driven websites, the vulnerability could facilitate large-scale attacks if weaponized. Attackers could leverage this flaw to deploy ransomware, steal sensitive information, or disrupt business operations. The requirement for authenticated access limits the attack surface but does not eliminate risk, as Editor-level accounts are common in many organizations and can be compromised through phishing or credential reuse.

1. Immediately update the AI Engine plugin to a patched version once available from the vendor. 2. Until a patch is released, restrict Editor-level and higher privileges to trusted users only, minimizing the number of accounts that can exploit this vulnerability. 3. Implement Web Application Firewall (WAF) rules to detect and block attempts to rename uploaded files to executable extensions via the update_media_metadata endpoint. 4. Monitor upload directories for suspicious file types and unexpected PHP files, and remove any unauthorized files promptly. 5. Harden server configurations to prevent execution of PHP files in upload directories by disabling PHP execution in those directories via .htaccess or server configuration. 6. Conduct regular audits of user privileges and remove unnecessary Editor or Administrator accounts. 7. Employ multi-factor authentication (MFA) to reduce the risk of account compromise. 8. Monitor logs for unusual REST API activity related to media metadata updates. These steps collectively reduce the risk of exploitation and limit potential damage.