CVE-2026-0746 is a Server-Side Request Forgery (SSRF) vulnerability identified in the AI Engine plugin for WordPress, specifically in the 'get_audio' function present in all versions up to and including 3.3.2. SSRF vulnerabilities allow attackers to induce the server to make HTTP requests to arbitrary locations, potentially accessing internal or protected resources that are not directly reachable from the outside. In this case, the vulnerability can be exploited by authenticated users with Subscriber-level privileges or higher, which is a relatively low privilege level in WordPress. The attack vector requires that the plugin's "Public API" setting is enabled and that the server configuration has 'allow_url_fopen' set to 'On', which permits PHP file functions to retrieve data from remote locations. When these conditions are met, an attacker can leverage the 'get_audio' function to send crafted requests from the server to internal services or external systems, potentially exposing sensitive information or modifying data if internal services accept such requests. The vulnerability impacts confidentiality and integrity but does not affect availability. The CVSS 3.1 base score is 6.4, reflecting medium severity with network attack vector, low attack complexity, requiring privileges but no user interaction, and a scope change due to the potential impact on other components beyond the vulnerable plugin. No public exploits have been reported yet, but the presence of this vulnerability in a widely used WordPress plugin makes it a significant concern for website administrators. The lack of available patches at the time of reporting necessitates immediate mitigation steps to reduce exposure.

The SSRF vulnerability in the AI Engine plugin can lead to unauthorized internal network reconnaissance and data exposure, as attackers can make the server send requests to internal services that are otherwise inaccessible externally. This can result in leakage of sensitive information such as internal APIs, databases, or metadata services. Additionally, if internal services accept and process these requests, attackers might manipulate or modify internal data, impacting data integrity. Since the vulnerability requires only Subscriber-level authentication, it lowers the barrier for exploitation, especially on sites allowing user registrations. The impact is primarily on confidentiality and integrity, with no direct availability impact. Organizations running WordPress sites with this plugin enabled and configured with the vulnerable settings face increased risk of internal network compromise, data breaches, and lateral movement by attackers. This risk is heightened for organizations with sensitive internal services behind the web server and those that enable the Public API feature. The medium CVSS score reflects a moderate but actionable threat that could be leveraged as part of a broader attack chain.

1. Immediately disable the "Public API" feature in the AI Engine plugin settings if it is not essential to your operations. 2. If possible, set the PHP configuration directive 'allow_url_fopen' to 'Off' to prevent PHP functions from fetching remote URLs, reducing SSRF attack surface. 3. Restrict Subscriber-level user registrations or review user privileges to limit potential attacker access. 4. Monitor web server and application logs for unusual outbound requests originating from the 'get_audio' function or related plugin activities. 5. Implement network-level egress filtering to restrict the web server from making unauthorized outbound HTTP requests to internal or sensitive services. 6. Apply the vendor's patch or update the AI Engine plugin to a fixed version once available. 7. Conduct internal audits of exposed internal services to ensure they are not vulnerable to unauthorized requests. 8. Employ Web Application Firewalls (WAFs) with rules to detect and block SSRF attempts targeting the plugin's endpoints. These steps collectively reduce the risk of exploitation and limit the potential damage from this vulnerability.