CVE-2026-12511: AI Engine WordPress Path Traversal Flaw

CVE-2026-12511 Overview

CVE-2026-12511 is a path traversal vulnerability in the AI Engine WordPress plugin versions prior to 3.5.5. The plugin fails to sanitize user-supplied filenames before writing downloaded file contents to disk. Authenticated users with editor-level access can supply crafted filenames containing directory traversal sequences to write attacker-controlled bytes to arbitrary locations on the server. Successful exploitation can lead to remote code execution when attackers overwrite PHP files within the web root or plugin directories.

Critical Impact
Authenticated editors can write arbitrary bytes anywhere the web server user has write permissions, enabling webshell placement and full site compromise.

Affected Products

AI Engine WordPress plugin versions before 3.5.5
WordPress sites permitting editor-level accounts with the plugin installed
Any hosting environment where the PHP process has write access to executable paths

Discovery Timeline

2026-07-14 - CVE-2026-12511 published to the National Vulnerability Database
2026-07-14 - Last updated in NVD database

Technical Details for CVE-2026-12511

Vulnerability Analysis

The AI Engine plugin exposes functionality that downloads remote content and writes it to the WordPress filesystem. The download handler accepts a filename parameter from an authenticated request and concatenates it into a destination path without validating traversal sequences. An editor-level user can submit ../ segments in the filename to escape the intended upload directory and target arbitrary paths.

Because the response body written to disk is also attacker-controlled, the primitive is not a simple file overwrite but an arbitrary file write with chosen contents. On typical WordPress deployments, writing a PHP payload into wp-content/, wp-includes/, or a plugin directory achieves remote code execution under the web server user.

The attack requires authentication with the editor role or higher, which limits mass exploitation but remains practical in multi-author sites, compromised credential scenarios, and environments where editor accounts are widely distributed. The vulnerability is classified as path traversal [CWE-22] leading to arbitrary file write.

Root Cause

The root cause is missing input sanitization on the filename parameter passed to the download-and-write routine. The code does not call basename(), does not reject .. sequences, and does not enforce that the resolved path stays within an allowed directory using canonicalization checks such as realpath() comparison.

Attack Vector

An authenticated attacker with editor privileges issues a request to the vulnerable AI Engine endpoint containing a filename value such as ../../../../wp-content/plugins/target/shell.php alongside a URL pointing to attacker-hosted PHP content. The plugin fetches the remote content and writes it to the resolved traversal path. The attacker then requests the written file through the web server to execute the payload. Full technical details are available in the WPScan Vulnerability Advisory.

Detection Methods for CVE-2026-12511

Indicators of Compromise

Unexpected .php files appearing in wp-content/uploads/, plugin directories, or wp-includes/ with recent modification timestamps
Outbound HTTP requests from the WordPress host to unknown domains initiated by the AI Engine plugin
POST requests to AI Engine plugin endpoints containing ../ or URL-encoded %2e%2e%2f sequences in filename parameters
Web server access logs showing requests to newly created PHP files under upload directories

Detection Strategies

Inspect WordPress request logs for AI Engine plugin endpoints carrying filename parameters with traversal patterns
Monitor filesystem changes to WordPress directories using file integrity monitoring baselines
Alert on PHP file creation events under paths that should be static content only, such as wp-content/uploads/
Correlate editor-account authentication events with subsequent plugin API calls and file writes

Monitoring Recommendations

Enable WordPress audit logging for editor and administrator actions, including plugin endpoint invocations
Forward web server, PHP error, and WordPress logs to a centralized platform for correlation and retention
Track outbound network connections from the PHP process and flag connections to non-approved destinations
Review new file creation events on production WordPress hosts on a daily cadence

How to Mitigate CVE-2026-12511

Immediate Actions Required

Upgrade the AI Engine WordPress plugin to version 3.5.5 or later on all sites
Audit editor-level and higher accounts and remove or downgrade any that are inactive or unnecessary
Rotate credentials for all editor and administrator accounts if compromise is suspected
Scan the WordPress filesystem for unauthorized PHP files, particularly under upload and plugin directories

Patch Information

The vendor addressed the vulnerability in AI Engine version 3.5.5 by sanitizing the filename input before writing files. Administrators should apply the update through the WordPress plugin manager or WP-CLI. Details are documented in the WPScan Vulnerability Advisory.

Workarounds

Deactivate the AI Engine plugin until the patched version can be applied
Restrict editor role assignments and enforce multi-factor authentication for all privileged WordPress accounts
Deploy a web application firewall rule blocking requests to AI Engine endpoints containing traversal sequences such as ../ or %2e%2e%2f
Configure the web server to deny PHP execution within wp-content/uploads/ using directory-level rules

bash

# Apache configuration to block PHP execution in uploads directory
<Directory "/var/www/html/wp-content/uploads">
    <FilesMatch "\.(php|phtml|phar)$">
        Require all denied
    </FilesMatch>
</Directory>

# WP-CLI command to update the plugin
wp plugin update ai-engine --version=3.5.5