The AI Engine WordPress plugin before 3.7.9 does not check that the item passed to one of its media actions belongs to the requesting user before converting it to an attachment and permanently deleting it, allowing users with the Editor role and above to delete arbitrary posts of any type, including content they cannot otherwise delete such as navigation menus, block templates and global styles.

The AI Engine WordPress plugin before 3.7.9 does not verify that the user performing certain AI media management actions owns or is otherwise allowed to edit the targeted object, allowing users with the Editor role or above to modify, or change the type of, arbitrary posts on the site, including content they are not permitted to edit.

Missing Authorization vulnerability in Meow Apps AI Engine ai-engine allows Exploiting Incorrectly Configured Access Control Security Levels.This issue affects AI Engine: from n/a through 3.8.3.

The AI Engine – The Chatbot, AI Framework & MCP for WordPress plugin for WordPress is vulnerable to Stored Cross-Site Scripting in versions up to, and including, 3.8.0 This is due to a chain of missing input neutralization and output escaping across the /mwai-ui/v1/chats/submit REST endpoint, the PHP error-log parser (MeowKitMWAIHelpers::phperrorlogs), the Advisor task (MeowMWAIModulesAdvisor::runadvisor), and the Advisor dashboard widget (advisormetabox): the server-parameter denylist in chatsubmit strips only exact key names such as 'model' while convertkeys() later canonicalizes 'model' back to 'model', allowing an unauthenticated caller to place an attacker-controlled string (including CR/LF) into $query->model; finalchecks() throws an Exception whose message embeds that raw string, and the non-streaming, non-admin catch branch writes it to the PHP error log unmodified — creating a forged log line that the plugin's own parser subsequently returns as recent PHP-error content; runadvisor() then appends that content verbatim to the AI prompt (indirect prompt injection — CWE-1427), the returned JSON is stored in the mwaiadvisordata option with no schema validation or HTML sanitization, and advisormetabox() concatenates the resulting 'title' and 'description' values directly into the WordPress dashboard widget without eschtml(), wpkses(), or equivalent escaping. This makes it possible for unauthenticated attackers to inject arbitrary web scripts in pages that will execute whenever an administrator accesses the WordPress dashboard.

Unauthenticated Insecure Direct Object References (IDOR) in AI Engine <= 3.7.8 versions.