CVE-2024-34440: AI Engine ChatGPT Chatbot File Upload Flaw

CVE-2024-34440 Overview

CVE-2024-34440 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.2.63. An authenticated attacker with high privileges can upload files of a dangerous type through the plugin, bypassing type restrictions intended to block executable content. Successful exploitation compromises confidentiality, integrity, and availability of the underlying WordPress site. The weakness maps to CWE-434: Unrestricted Upload of File with Dangerous Type.

Critical Impact
Authenticated attackers can upload arbitrary files to a vulnerable WordPress site, enabling web shell deployment and full server compromise.

Affected Products

Jordy Meow AI Engine: ChatGPT Chatbot plugin for WordPress
All versions from n/a through 2.2.63
WordPress sites running the meowapps:ai_engine component

Discovery Timeline

2024-05-14 - CVE-2024-34440 published to NVD
2026-06-17 - Last updated in NVD database

Technical Details for CVE-2024-34440

Vulnerability Analysis

The AI Engine: ChatGPT Chatbot plugin exposes functionality that accepts file uploads without adequately validating the file type or extension. The plugin fails to enforce an allow-list of safe MIME types and does not verify uploaded content against expected chatbot assets. As a result, an attacker holding a privileged WordPress account can submit files with executable extensions such as .php, .phtml, or .phar. The uploaded files land within the WordPress wp-content directory tree, where they remain reachable through the web server. Because the WordPress host executes PHP by default in these paths, uploaded scripts run in the site's security context.

Root Cause

The root cause is missing or insufficient server-side validation of uploaded file content and extension in the plugin's upload handler. The plugin trusts client-supplied filenames and MIME headers instead of enforcing a strict allow-list. This falls squarely under CWE-434.

Attack Vector

Exploitation requires network access to the WordPress site and an authenticated account with high privileges, such as an administrator or an author-tier role granted upload capabilities. No user interaction is required. The attacker sends a crafted multipart request to the plugin's upload endpoint carrying a PHP payload disguised as a supported asset. Once written to disk, the attacker requests the uploaded file directly to execute arbitrary PHP, establishing a web shell, exfiltrating data, or pivoting into the host. See the Patchstack Vulnerability Report for advisory details.

No verified public proof-of-concept code is available; refer to the Patchstack advisory for further technical context.

Detection Methods for CVE-2024-34440

Indicators of Compromise

New or unexpected files with executable extensions (.php, .phtml, .phar, .pht) under wp-content/uploads/ or plugin-controlled directories.
Outbound connections from the web server to unfamiliar hosts shortly after plugin upload activity.
WordPress accounts with elevated privileges creating uploads outside their normal working hours.
Web server access logs showing direct GET requests to newly uploaded PHP files immediately after POST requests to plugin upload endpoints.

Detection Strategies

Monitor WordPress uploads directories for creation of files whose extension or magic bytes indicate server-executable content.
Alert on HTTP POST requests to AI Engine plugin endpoints followed by GET requests to the same path in wp-content.
Correlate WordPress audit logs with file system telemetry to attribute uploads to specific privileged accounts.

Monitoring Recommendations

Enable file integrity monitoring on the WordPress installation, focusing on the wp-content/uploads/ and wp-content/plugins/ai-engine/ trees.
Forward web server access logs and PHP execution logs to a centralized analytics platform for retention and correlation.
Track authentication events for administrator accounts and flag privilege changes to WordPress users.

How to Mitigate CVE-2024-34440

Immediate Actions Required

Update the AI Engine: ChatGPT Chatbot plugin to a version later than 2.2.63 that addresses the file upload validation issue.
Audit the WordPress wp-content/uploads/ directory for unexpected PHP or other executable files and remove any that are not legitimate.
Rotate credentials for all administrator and privileged WordPress accounts, and review the user list for unauthorized additions.
Review web server access logs for evidence of prior exploitation attempts against the plugin's upload endpoints.

Patch Information

The vendor Jordy Meow (meowapps) has released fixed versions of the AI Engine plugin following the versions affected through 2.2.63. Consult the Patchstack advisory and the WordPress plugin repository to confirm the current fixed release and apply the update through the WordPress admin dashboard or via WP-CLI.

Workarounds

Restrict administrator and upload-capable roles to a minimal set of trusted users until the patch is applied.
Deploy a web application firewall rule that blocks requests carrying PHP or other executable payloads to the plugin's upload endpoints.
Configure the web server to deny execution of PHP files within wp-content/uploads/ using directives such as an Apache <FilesMatch> block or an Nginx location rule.
Temporarily deactivate the AI Engine: ChatGPT Chatbot plugin if immediate patching is not feasible.

bash

# Nginx: prevent PHP execution inside the WordPress uploads directory
location ~* /wp-content/uploads/.*\.(php|phtml|phar|pht)$ {
    deny all;
    return 403;
}