MagicAI for WordPress EUVD-2026-65165

Exploitation requires a valid subscriber-level (or higher) WordPress account on the target site. Sites with open user registration allow any internet user to obtain this credential at no cost. The vulnerability is triggered through a network request to the affected plugin's endpoint - no physical or local access is needed. The flaw is within MagicAI for WordPress version 1.4 or earlier; updated versions are not confirmed affected. Exploitation is further constrained by PHP's include path configuration and server filesystem permissions: achieving code execution (beyond information disclosure) typically requires a writable, web-accessible upload path that can hold attacker-supplied PHP content. Sites that disable file uploads or restrict PHP execution in upload directories limit the worst-case impact to information disclosure rather than full RCE.

The CVSS 3.1 vector CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H reflects a network-reachable, low-complexity flaw requiring only a subscriber account - the lowest registered WordPress user role - making exploitation accessible to any registered user on a site with open registration. The full C:H/I:H/A:H triad indicates the flaw can result in complete compromise of the WordPress installation. No EPSS score was provided in source data, and the vulnerability is not listed in the CISA KEV catalog, so confirmed active exploitation cannot be asserted. However, LFI vulnerabilities in WordPress plugins with subscriber-level access are routinely chained with file-upload features to achieve RCE, meaning even a mid-sized municipal IT team in rybnik - as a hypothetical example of an organization running AI-enhanced WordPress sites - should treat this as an urgent patching priority rather than a low-likelihood theoretical risk. The absence of a public exploit or KEV listing tempers immediate alarm, but the low privilege bar and full-impact CVSS metrics make this a genuine priority for any site with open subscriber registration.

An attacker registers a free subscriber account on a WordPress site running MagicAI for WordPress 1.4 or earlier. The attacker submits a crafted request to a plugin endpoint, manipulating a filename parameter to include a PHP file from the server filesystem - for example, a file previously uploaded via the plugin's AI content generation features. If a PHP-executable upload path is reachable, this escalates to remote code execution under the web server's process identity.