AI Engine permits arbitrary local file read and off-site exfiltration
AI Engine before 3.7.2 maps a caller-supplied URL to a local path without confining it, reads the selected file, and forwards its contents to an external service. A Subscriber can exploit this when the non-default public API is enabled; otherwise an Administrator can reach it, including a multisite subsite administrator reading network-shared secrets.
- Component
- AI Engine
- Plugin slug
ai-engine- Affected
- 3.3.3 to < 3.7.2
- Safe version
3.7.2- Published
- Aug 26, 2026
This CVE was published Aug 26, 2026 and is one of 35 known issues for this plugin.
Update, patch or deactivate.
Update to 3.7.2 or later, disable the public API unless required, review outbound AI requests, and rotate secrets if local configuration files may have been exposed.
A safe version is available, so updating to that version or later is the preferred remediation. If an immediate update is not practical, consider a targeted application patch or temporarily restricting the affected functionality.
Deactivate only when warranted by your risk profile, or when advised by your hosting provider in the limited circumstances where the vulnerability cannot otherwise be mitigated. If you’re unsure which action is appropriate, contact Fused or your hosting provider for guidance.
Technical description
The AI Engine WordPress plugin before 3.7.2 does not confine a caller-supplied URL when mapping it to a local filesystem path before reading the file and forwarding its contents to an external service, allowing users with a subscriber-level account to read arbitrary files from the server and exfiltrate them off-host. Reaching the issue at subscriber level requires a non-default public API feature to be enabled; otherwise the same issue is reachable by an administrator, which on multisite allows a non-super subsite administrator to read the network-shared configuration and its secrets.
CVE / CNA vector: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:N/A:N