CVE-2026-75797: AI Engine 3.3.3 - 3.7.1 - Subscriber+ Arbitrary File Read via 'url' Parameter
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.
Affected Software
Remediation
Recommended actions to resolve this vulnerability, in priority order.
- Upgrade
Upgrade
AI Engine WordPress pluginto a version that resolves this vulnerability.Fixed in 3.7.2 - Configuration
If using multisite subscriber-level access, ensure the non-default public API feature required for reaching the issue at subscriber level is disabled (so the vulnerability is not reachable at subscriber level).
AI Engine WordPress plugin public API feature = non-default (enabled) -> disable
Event History
Frequently Asked Questions
Who can exploit this in a default installation?
Without the non-default public API feature enabled, the issue is reachable by an administrator. On WordPress multisite, a non-super administrator of a subsite can use it to read network-shared configuration and associated secrets.
When can a subscriber-level account exploit the issue?
Subscriber-level exploitation requires the plugin's non-default public API feature to be enabled. With that feature enabled, a subscriber can supply a URL that is mapped to a local path and have arbitrary server files read and sent to an external service.
What is the impact of successful exploitation?
An attacker can read arbitrary files from the server. The plugin forwards the file contents to an external service, creating an off-host data-exfiltration path.