CVE-2026-75797
HighCVSS 7.7Exploitation Probability (EPSS)
Low risk9th percentile - higher than 9% of all known CVEs
Summary
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.
Risk Assessment
Users with low privileges can read sensitive files such as configuration and secrets, potentially leading to data leakage and further attacks.
Recommendation
Update the AI Engine plugin to version 3.7.2 or later and disable non-default public API features if not needed.
Other vulnerabilities in AI Engine WordPress plugin
See all- CVE-2026-75796High
The AI Engine WordPress plugin before 3.6.1 does not verify that the requesting user is authorized to act on the targeted account before performing privileged user management operations, allowing users with the Administrator role on a Multisite sub-site to take over any account on the network, including the Network Administrator's.
- CVE-2026-16953Medium
The AI Engine WordPress plugin before version 3.6.4 does not verify ownership of a guest's uploaded files before deletion, relying solely on a client-supplied session cookie value for authorization. An unauthenticated attacker who obtains a victim's session identifier and file reference can delete the victim's uploaded files.
- CVE-2026-16954Medium
The AI Engine WordPress plugin before version 3.6.4 does not redact secret configuration values before exposing them in an admin page's inline script data, allowing users with the Editor role to read the site's stored third-party API key and authentication tokens in cleartext, despite those secrets being restricted to administrators everywhere else.
- CVE-2026-12511High
The AI Engine WordPress plugin before version 3.5.5 does not sanitize a user-supplied filename before using it to write a downloaded file, allowing authenticated users with editor-level access to write attacker-controlled bytes to an arbitrary location on the server via path traversal.
Original NVD description (English source)
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.