AI Engine EUVD-2026-111565

Three concrete prerequisites must all hold: (1) the attacker has an authenticated account with subscriber-level access or above (PR:L); (2) the site administrator has explicitly enabled the plugin's Public API option, which is not the default state; and (3) the plugin's scheduled hourly cleanup_files task must execute after the malicious upload for the deletion to occur. These conditions - particularly the non-default Public API requirement and the dependency on cron-task timing - are the stated factors that limit exploitation and justify the AC:H / Medium rating; impact is bounded to deletion of media files only, with no confidentiality exposure.

This is a genuinely low-priority issue despite being network-reachable. The CVSS 3.1 vector (AV:N/AC:H/PR:L/UI:N/S:U/C:N/I:L/A:L, base 4.2 Medium) already encodes the limiting factors: AC:H reflects that exploitation is conditional, PR:L requires an authenticated subscriber account, and impact is confined to integrity/availability (I:L/A:L) with no confidentiality loss - the flaw only deletes media files, not arbitrary system files. The vuln.today decision label is 'this_month', not act_now or emergency, consistent with the low real-world urgency. No EPSS score, no CISA KEV listing, and no verified working exploit code were provided - the references are the Wordfence advisory plus WordPress trac source-code and changeset links, which document the code and fix but are not an exploit. The practical risk is further suppressed by two stacked preconditions (administrator must have enabled the non-default Public API option, and the hourly cleanup_files task must run after the malicious upload), which together explain the AC:H rating. Net: a real but low-severity, config-dependent defect appropriate for routine monthly patching, not an emergency.

On a WordPress site running AI Engine ≤3.8.4 where the administrator has enabled the Public API option, an attacker who holds (or registers for) a subscriber-level account abuses insufficient path validation in the upload_file function to point a file operation at media files outside the intended location. The deletion is not immediate - it is realized when the plugin's hourly cleanup_files task next runs, which is why the attack is rated high-complexity. No public working exploit code was identified at time of analysis.