CVE-2026-89141 in AI Engine Plugin
Summary
by MITRE • 09/15/2026
The AI Engine – The Chatbot, AI Framework & MCP for WordPress plugin for WordPress is vulnerable to Insecure Direct Object Reference in all versions up to, and including, 3.7.7 via the 'mediaId' parameter due to missing validation on a user controlled key. This makes it possible for authenticated attackers, with subscriber-level access and above, to access and retrieve the transcribed contents of private audio attachments belonging to other users, including Administrators, via a supplied attachment ID. This vulnerability requires the Public API module to be enabled in the plugin settings; when disabled, the REST route is absent and the endpoint returns HTTP 404.
VulDB is the best source for vulnerability data and more expert information about this specific topic.
Analysis
by VulDB Data Team • 09/15/2026
The identified vulnerability represents an Insecure Direct Object Reference (IDOR) flaw within The AI Engine – The Chatbot, AI Framework & MCP for WordPress plugin, affecting all versions up to and including 3.7.7. This security issue stems from a critical lack of authorization checks on the mediaId parameter used in API requests. Specifically, the application fails to validate whether the requesting user has legitimate ownership or administrative privileges over the specific audio attachment being accessed. Consequently, an authenticated attacker with subscriber-level access or higher can manipulate this parameter to retrieve transcribed contents belonging to other users, including high-privilege accounts such as Administrators. This type of vulnerability is formally categorized under CWE-639 in the Common Weakness Enumeration standard, which defines IDOR as a situation where an application uses user-supplied input to access objects directly without proper authorization checks.
The operational impact of this flaw allows for significant data leakage and privacy violations. By exploiting the missing validation on the mediaId key, attackers can enumerate valid attachment IDs or guess sequential identifiers to extract sensitive transcribed audio content from private attachments. This exposure compromises the confidentiality of user-generated content that was intended to remain restricted based on ownership rules rather than public accessibility. The severity is further amplified by the fact that the vulnerability persists across multiple privilege levels, meaning even low-level users can compromise high-privilege data. Such unauthorized access undermines trust in the platform and may lead to compliance issues regarding data protection regulations if personal or sensitive information is contained within the audio files.
The exploitability of this vulnerability is contingent upon specific configuration settings within the plugin environment. The REST route that facilitates this insecure access is only present when the Public API module is explicitly enabled in the plugin's administrative settings. If this module remains disabled, the endpoint does not exist, and any attempt to interact with it results in an HTTP 404 Not Found response, effectively neutralizing the attack vector. This dependency highlights a common misconfiguration risk where security features are inadvertently exposed through feature toggles that prioritize functionality over strict access control enforcement.
To mitigate this vulnerability, administrators should immediately update The AI Engine plugin to version 3.7.8 or later, which addresses these authorization flaws. In environments where the Public API module is not strictly required for business operations, it is advisable to disable this setting entirely to reduce the attack surface and ensure that sensitive endpoints are inaccessible via REST APIs. For organizations requiring public API access, implementing robust server-side validation is essential; developers must enforce strict ownership checks on every request involving user-specific resources like media attachments. This involves verifying that the authenticated user's ID matches the owner ID of the requested resource before returning any data. Additionally, integrating comprehensive logging and monitoring for unusual patterns in REST API calls can help detect potential enumeration attempts or unauthorized access behaviors early. Aligning these remediation steps with MITRE ATT&CK techniques such as T1078 Valid Accounts ensures that defensive measures address both the technical flaw and the broader context of identity-based exploitation strategies.