CVE-2026-32560: MagicAI WordPress Path Traversal Flaw

CVE-2026-32560 Overview

CVE-2026-32560 is a Local File Inclusion (LFI) vulnerability affecting the MagicAI for WordPress plugin, which provides AI text, image, chat, code, and voice generation features. The flaw impacts versions up to and including 1.4. Authenticated users with subscriber-level privileges can exploit the vulnerability to include arbitrary local files through the plugin. The weakness is tracked under CWE-98, improper control of filename for include/require statement in PHP programs.

Critical Impact
An authenticated subscriber can trigger local file inclusion in the MagicAI plugin, leading to disclosure of sensitive files and potential code execution on the WordPress host.

Affected Products

MagicAI for WordPress - AI Text, Image, Chat, Code, and Voice Generator plugin
All versions up to and including 1.4
WordPress sites running the vulnerable plugin with subscriber registration enabled

Discovery Timeline

2026-08-24 - CVE-2026-32560 published to NVD
2026-08-26 - Last updated in NVD database

Technical Details for CVE-2026-32560

Vulnerability Analysis

The MagicAI for WordPress plugin exposes a request handler that constructs a file path from user-controlled input and passes it to a PHP include or require statement. Because the plugin does not sufficiently validate or sanitize the supplied parameter, an attacker can traverse the filesystem and load files outside the intended directory. The endpoint is reachable by authenticated users at the subscriber level, the lowest privileged role in WordPress. This significantly widens the attack surface, since WordPress sites frequently allow open user registration.

Root Cause

The root cause is improper control of the filename passed to a PHP include/require call [CWE-98]. The plugin trusts request parameters to reference internal template or module files without enforcing an allowlist or canonicalizing the resulting path. Path traversal sequences and absolute paths are not stripped before file resolution.

Attack Vector

An attacker registers or authenticates as a subscriber and issues a crafted HTTP request to the vulnerable MagicAI endpoint. The request supplies a manipulated file parameter that resolves to a sensitive local file such as wp-config.php, log files, session stores, or uploaded content. When PHP includes an attacker-controlled file, the contents are executed as PHP, converting file disclosure into code execution when writable or attacker-influenced files can be reached. Refer to the Patchstack Vulnerability Report for advisory details.

Detection Methods for CVE-2026-32560

Indicators of Compromise

HTTP requests to MagicAI plugin endpoints containing traversal sequences such as ../, encoded variants like %2e%2e%2f, or absolute paths beginning with /
Access to wp-config.php, /etc/passwd, or PHP session files originating from the web server process
Unexpected subscriber account registrations followed shortly by requests to magicai-wp plugin routes
New or modified PHP files under wp-content/uploads/ that are later referenced by plugin parameters

Detection Strategies

Inspect WordPress access logs for authenticated requests to MagicAI plugin URLs carrying suspicious file, path, template, or page parameters
Deploy web application firewall rules that block path traversal patterns and null byte injection against /wp-admin/admin-ajax.php and plugin routes
Correlate low-privileged user sessions with reads of sensitive server files using file integrity monitoring

Monitoring Recommendations

Alert on PHP include/require failures in web server error logs referencing user-controlled paths
Monitor for outbound connections from the WordPress host immediately following subscriber-authenticated plugin requests
Track spikes in new subscriber registrations that precede plugin interaction

How to Mitigate CVE-2026-32560

Immediate Actions Required

Update MagicAI for WordPress to a version later than 1.4 as soon as the vendor publishes a fixed release
Temporarily disable the MagicAI plugin if a patched version is not yet available
Disable open user registration or restrict the default new user role to prevent unauthenticated actors from obtaining subscriber access
Rotate WordPress secrets in wp-config.php and database credentials if exploitation is suspected

Patch Information

Consult the Patchstack Vulnerability Report for the latest fixed version and vendor guidance. At time of publication, all versions through 1.4 are affected.

Workarounds

Restrict access to the plugin's endpoints via web server rules until a patch is applied
Enforce a WAF ruleset that blocks path traversal, null bytes, and absolute paths in query and POST parameters
Set open_basedir in PHP configuration to constrain file inclusion to the WordPress installation directory
Audit and remove untrusted subscriber accounts created during the exposure window

bash

# Example PHP hardening in php.ini or a per-site .user.ini
open_basedir = "/var/www/wordpress:/tmp"
allow_url_include = Off
allow_url_fopen = Off