EUVD-2026-66281
GHSA-v7cm-6545-2w7m
Severity by source
AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:N/A:N
Network-accessible read with scope change justified; PR:L reflects worst-case subscriber vector when public API is enabled, consistent with standard CVSS worst-case scoring practice.
Primary rating from Vendor (WPScan).
CVSS VectorVendor: WPScan
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:N/A:N
Lifecycle Timeline
5DescriptionCVE.org
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.
AnalysisAI
Path traversal in the AI Engine WordPress plugin (versions 3.3.3 through 3.7.1) allows arbitrary server file reads with subsequent exfiltration to an external service. When the plugin's non-default public API feature is enabled, subscriber-level users can supply a crafted URL that the plugin maps to a local filesystem path without confinement, reads, and forwards to an external AI endpoint. …
Unlock full vulnerability intelligence
- Risk assessment & exploitation conditions
- Attack chain visualization
- Remediation with exact patch versions
- Threat intelligence from 22 sources
- Personal watchlist & email alerts
Free forever · No credit card required
Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata
Vulnerability AssessmentAI
| Exploitation | Subscriber-level exploitation requires the AI Engine plugin's 'public API' feature to be explicitly enabled by a site administrator - this is a non-default configuration, so most single-site WordPress installations are not exposed to low-privilege attacks. … Additional conditions and limiting factors are described in the full assessment. |
| Risk Assessment | CVSS 3.1 scores this at 7.7 (High) with AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:N/A:N, reflecting network-accessible exploitation requiring only subscriber credentials, no user interaction, a scope change across the security boundary, and high confidentiality impact. … Full risk analysis with EPSS, KEV, and SSVC signal comparison available after sign-in. |
| Exploit Scenario | An attacker registers or obtains a subscriber-level account on a WordPress site with AI Engine installed and the public API feature enabled, then submits a crafted request with a URL containing path traversal sequences targeting sensitive files such as wp-config.php or server-level credentials. The plugin resolves the path without confinement, reads the file, and automatically forwards its contents to an external AI service endpoint configured by the attacker or accessible to them - completing a full read-and-exfiltrate chain in a single request. … |
| Remediation | Update the AI Engine WordPress plugin to version 3.7.2 or later, the vendor-released patch confirmed by WPScan (https://wpscan.com/vulnerability/1048b130-9263-4780-b886-656a891de85a/) and EUVD-2026-66281. … Detailed patch versions, workarounds, and compensating controls in full report. |
Recommended ActionAI
Within 24 hours: audit all WordPress instances running AI Engine plugin versions 3.3.3 through 3.7.1 and disable the public API feature if enabled to reduce exposure. …
Sign in for detailed remediation steps and compensating controls.
Threat intelligence, references, and detailed analysis are available after sign-in.
Unrestricted file upload in Jordy Meow's AI Engine: ChatGPT Chatbot plugin for WordPress (versions up to and including 1
Arbitrary file write in the AI Engine WordPress plugin before 3.5.5 lets authenticated editor-level users abuse an unsan
Privilege escalation in the AI Engine WordPress plugin (versions 2.8.0 through 3.6.0) enables any sub-site Administrator
The AI Engine WordPress plugin before 2.6.5 does not sanitize and escape a parameter from one of its RESP API endpoint b
AI Engine < 2.4.3 is susceptible to remote-code-execution (RCE) via Log Poisoning. Rated high severity (CVSS 7.2), this
Server-Side Request Forgery (SSRF) vulnerability in Jordy Meow AI Engine: ChatGPT Chatbot.1.4. Rated medium severity (CV
Cleartext exposure of third-party API keys and authentication tokens in AI Engine WordPress plugin (before 3.6.4) allows
Unauthorized access to private chatbot conversations in the AI Engine WordPress plugin before 3.5.5 allows any authentic
Unauthenticated remote attackers can invoke AI queries against a site owner's configured provider account through the AI
Unrestricted Upload of File with Dangerous Type vulnerability in Jordy Meow AI Engine: ChatGPT Chatbot.2.63. Rated criti
Unrestricted Upload of File with Dangerous Type vulnerability in Jordy Meow AI Engine: ChatGPT Chatbot.1.4. Rated critic
Path traversal in the AI Engine WordPress plugin before 3.6.6 allows server-side file contents to be read and exfiltrate
Same weakness CWE-22 – Path Traversal
View allSame technique Path Traversal
View allShare
External POC / Exploit Code
Leaving vuln.today