Severity by source
AV:N/AC:L/PR:L/UI:N/S:C/C:L/I:N/A:N
C:H reflects that arbitrary file read exposes wp-config.php secrets; S:C retained due to off-host exfiltration; PR:L scores worst-case subscriber path.
Primary rating from Vendor (WPScan).
CVSS VectorVendor: WPScan
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:L/I:N/A:N
Lifecycle Timeline
5DescriptionCVE.org
The AI Engine WordPress plugin before 3.6.6 does not confine a caller-supplied file path before reading it and forwarding the 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 before 3.6.6 allows server-side file contents to be read and exfiltrated to an external AI service without path sanitization. When the plugin's public API feature is enabled (a non-default setting), subscriber-level users can trigger this; otherwise the same flaw is accessible to WordPress administrators - and on multisite installations, a non-super subsite administrator can exploit it to read network-wide configuration files and extract embedded secrets such as database credentials and API keys. …
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 (CVSS PR:L path) requires the AI Engine plugin's public API feature to be explicitly enabled, which is a non-default configuration - without it, this attack path is unavailable to subscriber accounts. … Additional conditions and limiting factors are described in the full assessment. |
| Risk Assessment | The official CVSS 3.1 score of 5.0 (AV:N/AC:L/PR:L/UI:N/S:C/C:L/I:N/A:N) is arguably conservative on confidentiality: the C:L rating understates the practical impact of arbitrary file read, which can expose wp-config.php and its embedded database credentials, secret salts, and API keys - data of high sensitivity. … Full risk analysis with EPSS, KEV, and SSVC signal comparison available after sign-in. |
| Exploit Scenario | An attacker registers or compromises a subscriber-level account on a WordPress site running AI Engine with the public API feature enabled, then sends a crafted API request supplying a path traversal string targeting wp-config.php (e.g., '../../wp-config.php'). The plugin reads the file without validation and forwards its contents - including database host, credentials, and secret keys - to an external AI service endpoint, from which the attacker retrieves the exfiltrated data. … |
| Remediation | Update the AI Engine WordPress plugin to version 3.6.6 or later, which contains the vendor-released patch as confirmed by WPScan (https://wpscan.com/vulnerability/1b413d84-61c7-4e19-a693-312d74f618ff/) and EUVD-2026-54745. … Detailed patch versions, workarounds, and compensating controls in full report. |
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
Path traversal in the AI Engine WordPress plugin (versions 3.3.3 through 3.7.1) allows arbitrary server file reads with
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
Same weakness CWE-22 – Path Traversal
View allSame technique Path Traversal
View allShare
External POC / Exploit Code
Leaving vuln.today
EUVD-2026-54745
GHSA-hgr8-39c9-344p