The AI Engine WordPress plugin, versions earlier than 3.7.2, fails to constrain a caller‑supplied URL before converting it into a local filesystem path. An attacker who can invoke the plugin’s API with a subscriber‑level account can supply any URL, causing the plugin to read the corresponding file on the server and forward its contents to an external service. The same flaw is reachable by an administrator, and on multisite installations even a non‑super subsite administrator can read network‑shared configuration files and their secrets. The impact is the disclosure of arbitrary server files and the exfiltration of sensitive data.

Vendors: AI Engine, a WordPress plugin. Affected products include AI Engine WordPress plugin versions 3.3.3 through 3.7.1. Any installation running those versions before the 3.7.2 release is vulnerable.

The vulnerability is exploitable via the plugin’s externally exposed API endpoint that accepts a 'url' parameter. Reaching it requires enabling a non‑default public API setting; otherwise, administrators can trigger the flaw directly. Because the flaw allows an attacker to read files and send them to an external service, it could expose configuration data, credentials, or other internal information. No CVSS score is currently listed, and the EPSS score is not available; the vulnerability is not in the CISA KEV catalog. Attackers would need network access to the WordPress site and the ability to invoke the public API, which is the likely attack vector inferred from the description.