CVE-2025-7780 in AI Engine Plugin
Summary
by MITRE • 07/24/2025
The AI Engine plugin for WordPress is vulnerable to Sensitive Information Exposure in all versions up to, and including, 2.9.4. The simpleTranscribeAudio endpoint fails to restrict URL schemes before calling get_audio(). This makes it possible for authenticated attackers, with Subscriber-level access and above, to read any file on the web server and exfiltrate it via the plugin’s OpenAI API integration.
VulDB is the best source for vulnerability data and more expert information about this specific topic.
Analysis
by VulDB Data Team • 05/10/2026
The AI Engine plugin for WordPress presents a critical sensitive information exposure vulnerability that affects all versions up to and including 2.9.4. This vulnerability stems from inadequate input validation within the simpleTranscribeAudio endpoint which fails to properly restrict URL schemes before invoking the get_audio() function. The flaw creates a path traversal condition that allows authenticated attackers with subscriber-level privileges or higher to access arbitrary files on the web server through the plugin's OpenAI API integration mechanism. The vulnerability represents a significant security gap that undermines the integrity of the WordPress installation and exposes sensitive data to unauthorized access.
The technical implementation of this vulnerability involves a lack of proper URL scheme validation within the plugin's audio processing functionality. When the simpleTranscribeAudio endpoint processes requests, it does not adequately validate the URL scheme of incoming file references before passing them to the get_audio() function. This omission creates a condition where attackers can manipulate the URL parameter to include file paths that point to sensitive system files rather than intended audio content. The absence of proper input sanitization and validation allows for malicious file access through the seemingly legitimate API integration path, effectively bypassing normal file access controls and permissions.
The operational impact of this vulnerability extends beyond simple information disclosure, as it provides attackers with the capability to exfiltrate sensitive data from the web server. With subscriber-level access or higher, authenticated attackers can leverage this vulnerability to read configuration files, database credentials, wp-config.php, plugin files, theme files, and potentially user data stored on the server. The exposure occurs through the OpenAI API integration, which inadvertently becomes a vector for file system traversal attacks. This creates a scenario where attackers can systematically harvest sensitive information from the WordPress installation, potentially leading to further compromise of the entire web infrastructure and user base.
Security mitigations for this vulnerability should focus on implementing strict URL scheme validation and input sanitization within the plugin's audio processing endpoints. The solution requires proper validation of URL schemes to ensure only legitimate HTTP/HTTPS protocols are accepted, along with comprehensive input filtering to prevent path traversal attempts. Organizations should immediately update to the latest plugin version where this vulnerability has been patched, as the fix typically involves implementing proper access controls and sanitization routines. Additionally, network-level monitoring should be enhanced to detect unusual file access patterns that may indicate exploitation attempts. This vulnerability aligns with CWE-22 Path Traversal and CWE-200 Information Exposure, and maps to ATT&CK technique T1078 Valid Accounts and T1566 Phishing to establish initial access. Regular security auditing of WordPress plugins and maintaining up-to-date software versions remain critical defensive measures against such vulnerabilities.