CVE-2025-13380 is an Arbitrary File Read vulnerability identified in the AI Engine for WordPress: ChatGPT, GPT Content Generator plugin, affecting all versions up to and including 1.0.1. The root cause lies in insufficient validation of user-supplied file paths in the 'lqdai_update_post' AJAX endpoint, combined with the use of PHP's file_get_contents() function in the insert_image() function without enforcing protocol restrictions on URLs. This flaw allows authenticated attackers with Contributor-level access or higher to manipulate file path parameters to read arbitrary files on the server filesystem. Because file_get_contents() can be used with URLs, the lack of protocol restrictions could potentially be abused to read remote resources, though the primary impact is local file disclosure. The vulnerability is classified under CWE-73 (External Control of File Name or Path), indicating that external input directly influences file path operations without proper sanitization or validation. The CVSS v3.1 base score is 6.5, with an attack vector of network, low attack complexity, requiring privileges (Contributor or above), no user interaction, and a high impact on confidentiality, but no impact on integrity or availability. No patches or fixes are currently linked, and no known exploits have been observed in the wild as of the publication date (November 25, 2025).

The primary impact of this vulnerability is unauthorized disclosure of sensitive information stored on the web server hosting the vulnerable WordPress plugin. Attackers with Contributor-level access can read arbitrary files, which may include configuration files, database credentials, private keys, or other sensitive data. This can lead to further compromise of the web application or backend systems if attackers leverage the disclosed information. Since the vulnerability does not affect integrity or availability, it does not directly allow code execution or denial of service. However, the confidentiality breach can have severe consequences, including data leakage, privacy violations, and facilitating subsequent attacks such as privilege escalation or lateral movement. Organizations running WordPress sites with this plugin, especially those handling sensitive or regulated data, face increased risk of data breaches. The requirement for authenticated access limits exposure somewhat but does not eliminate risk, as Contributor-level accounts are common in multi-user WordPress environments.

To mitigate this vulnerability, organizations should first check for and apply any official patches or updates from the plugin vendor once available. In the absence of patches, immediate mitigation steps include restricting Contributor-level user privileges to trusted individuals only and auditing existing user accounts for unnecessary permissions. Implementing Web Application Firewall (WAF) rules to detect and block suspicious requests targeting the 'lqdai_update_post' AJAX endpoint with unusual file path parameters can reduce exploitation risk. Additionally, hardening the WordPress environment by disabling or limiting file system access for the web server user can help contain potential damage. Reviewing and sanitizing all user inputs related to file paths in custom code or plugins is recommended. Monitoring logs for anomalous access patterns to the AJAX endpoint may provide early detection of exploitation attempts. Finally, consider isolating the WordPress instance or running it in a containerized environment to limit the scope of file access.