Skip to main content
CVE Vulnerability Database
Vulnerability Database/CVE-2024-29100

CVE-2024-29100: Meowapps AI Engine RCE Vulnerability

CVE-2024-29100 is a remote code execution vulnerability in Meowapps AI Engine ChatGPT Chatbot caused by unrestricted file uploads. This post explains its impact, affected versions through 2.1.4, and mitigation steps.

Updated:

CVE-2024-29100 Overview

CVE-2024-29100 is an unrestricted file upload vulnerability in the Jordy Meow AI Engine: ChatGPT Chatbot plugin for WordPress. The flaw affects all versions up to and including 2.1.4. An authenticated attacker with high privileges can upload files of dangerous types to the server. Successful exploitation leads to arbitrary file execution and full compromise of the WordPress site. The issue is tracked under CWE-434: Unrestricted Upload of File with Dangerous Type.

Critical Impact

Attackers with high-privilege access can upload executable files to the WordPress host, resulting in remote code execution, data theft, and site takeover.

Affected Products

  • Jordy Meow AI Engine: ChatGPT Chatbot WordPress plugin, all versions through 2.1.4
  • WordPress sites running the meowapps/ai_engine plugin
  • Environments where the plugin is installed and reachable over the network

Discovery Timeline

  • 2024-03-28 - CVE-2024-29100 published to the National Vulnerability Database (NVD)
  • 2026-06-17 - Last updated in NVD database

Technical Details for CVE-2024-29100

Vulnerability Analysis

The AI Engine: ChatGPT Chatbot plugin exposes an upload handler that does not adequately validate the type of files being submitted. The handler accepts file extensions and MIME types that fall outside the plugin's intended scope, allowing server-executable content such as PHP scripts to be written to the WordPress uploads directory. Once written, the attacker can request the file directly through the web server to trigger execution. The vulnerability requires authenticated access with elevated privileges, which limits opportunistic exploitation but does not prevent post-compromise pivoting or insider abuse. Confidentiality, integrity, and availability are all impacted because arbitrary code executes in the context of the WordPress process.

Root Cause

The root cause is missing or insufficient allow-listing of file types in the plugin's upload logic. The plugin trusts client-supplied metadata rather than enforcing a strict allow-list of extensions and inspecting file content. This weakness maps to CWE-434.

Attack Vector

An authenticated attacker sends a crafted HTTP POST request to the vulnerable upload endpoint provided by the plugin. The request contains a payload with a dangerous extension, such as a PHP web shell. The plugin writes the file to a web-accessible directory. The attacker then issues an HTTP GET to the uploaded file's URL to execute arbitrary code on the host. Refer to the Patchstack Vulnerability Report for additional technical context.

Detection Methods for CVE-2024-29100

Indicators of Compromise

  • New files with executable extensions such as .php, .phtml, or .phar appearing in wp-content/uploads/ or plugin-managed upload paths
  • Outbound network connections from the WordPress host to unfamiliar IP addresses following a plugin upload event
  • Unexpected administrator or high-privilege user activity accessing the AI Engine upload endpoints
  • Web server access logs showing HTTP GET requests to newly created files in upload directories

Detection Strategies

  • Monitor WordPress plugin upload endpoints for POST requests containing non-media file extensions
  • Correlate file creation events in the uploads directory with subsequent HTTP requests to those files
  • Alert on modifications to files under wp-content/plugins/ai-engine/ that are inconsistent with vendor release hashes
  • Inventory WordPress deployments and flag installations running ai_engine at version 2.1.4 or earlier

Monitoring Recommendations

  • Enable file integrity monitoring on WordPress webroots, particularly wp-content/uploads/
  • Ship web server access logs and PHP error logs to a centralized analytics platform for behavioral analysis
  • Review WordPress audit logs for privileged accounts using the plugin's administrative functions
  • Track authentication events for administrator-level accounts to detect account takeover that could enable this exploit

How to Mitigate CVE-2024-29100

Immediate Actions Required

  • Update the AI Engine: ChatGPT Chatbot plugin to a version later than 2.1.4 as published by the vendor
  • Audit the wp-content/uploads/ directory for unexpected executable files and remove any that are identified
  • Rotate credentials for all administrator and high-privilege WordPress accounts
  • Review installed plugins and remove ai_engine if it is not actively required

Patch Information

The Patchstack Vulnerability Report confirms that the vulnerability affects versions up to and including 2.1.4. Administrators should upgrade to the fixed release provided by the plugin author through the WordPress plugin repository. Verify the installed version in the WordPress admin console under Plugins after upgrading.

Workarounds

  • Restrict administrator access to the WordPress backend through IP allow-lists or a web application firewall (WAF)
  • Configure the web server to deny PHP execution within the wp-content/uploads/ directory
  • Enforce multi-factor authentication for all high-privilege WordPress accounts to reduce the risk of credential-based exploitation
  • Temporarily deactivate the AI Engine: ChatGPT Chatbot plugin until the patched version is deployed

Disclaimer: This content was generated using AI. While we strive for accuracy, please verify critical information with official sources.

Default Legacy - Prefooter | Experience the World’s Most Advanced Cybersecurity Platform

Experience the Most Advanced Cybersecurity Platform

See how the world’s most intelligent, autonomous cybersecurity platform can protect your organization today and into the future.