CVE-2026-110976 in AI Engine Plugin
Summary
by MITRE • 10/18/2026
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.
Be aware that VulDB is the high quality source for vulnerability data.
Analysis
by VulDB Data Team • 10/18/2026
The vulnerability identified in the AI Engine WordPress plugin prior to version 3.7.9 represents a critical failure in access control logic within its media handling subsystem. This flaw specifically manifests during operations involving the conversion of items into attachments and their subsequent permanent deletion. The core technical deficiency lies in the absence of an ownership verification mechanism when processing these media actions. Specifically, the plugin fails to validate whether the item being targeted for deletion is actually owned by or associated with the user initiating the request. This lack of server-side authorization checks allows any authenticated user possessing at least Editor-level privileges to bypass standard WordPress permission boundaries and manipulate resources outside their designated scope.
From a technical perspective, this vulnerability exploits the trust placed in administrative roles without enforcing granular resource isolation. In typical WordPress architectures, while Editors have broad capabilities regarding content creation and modification, they are generally restricted from deleting system-critical elements such as navigation menus, block templates, or global styles unless explicitly granted those specific permissions by an Administrator. However, because the AI Engine plugin processes media actions through a function that does not cross-reference the item's metadata with the requesting user's identity, it effectively treats all items accessible to Editors as deletable regardless of their actual ownership status. This creates a path for unauthorized state changes where sensitive structural components of a WordPress site can be removed without proper authorization checks.
The operational impact of this vulnerability is significant and extends beyond simple content loss. By allowing the deletion of arbitrary posts of any type, attackers or malicious insiders with Editor access can destabilize website functionality. The ability to delete navigation menus disrupts user navigation and site structure, potentially leading to a denial of service for legitimate visitors. Furthermore, the removal of block templates and global styles alters the visual presentation and layout consistency of the entire WordPress installation, requiring significant effort to restore from backups or reconfigure. This level of disruption can severely compromise the integrity and availability of web applications relying on these structural elements.
In terms of industry standard classifications, this vulnerability aligns with CWE-269, which describes Improper Privilege Control, as it allows a user to perform actions beyond their assigned privileges. It also relates closely to CWE-732, involving Incorrect Permission Assignment for Critical Resource, because the plugin fails to enforce correct access controls on critical system resources like menus and templates. From an offensive security standpoint, this behavior is consistent with ATT&CK technique T1485, specifically Data Destruction, where an adversary modifies or destroys data to impact availability. The exploitation vector typically involves authenticated users leveraging API endpoints or frontend actions exposed by the plugin to trigger these unchecked deletion routines against targeted resources they do not own.
To mitigate this vulnerability, immediate action is required to update the AI Engine WordPress plugin to version 3.7.9 or later, where the developers have implemented proper ownership verification checks before processing media deletions. Administrators should also audit user roles and ensure that only trusted individuals hold Editor-level privileges if possible, adhering to the principle of least privilege. Additionally, implementing robust backup strategies is essential for recovery in case any damage has already occurred due to exploitation prior to patching. Regular security audits focusing on access control logic within custom plugins can help identify similar flaws before they are exploited in production environments.