EUVD-2026-85465
GHSA-5g4g-j86c-xv6v
Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain
-
AccessIdentify AI Engine endpoint
-
DeliveryEnumerate object identifiers
-
ExploitSend unauthenticated IDOR request
-
ExecutionRetrieve unauthorized data
-
ImpactConfidentiality disclosure
Vulnerability Assessment
| Weakness |
CWE
OWASP Top 10:2025
A01:2025 - Broken Access Control
ASVS 5.0
V8 - Authorization Object-level authorization, IDOR prevention
|
| Exploitation Conditions | Requires only network access to a WordPress site running AI Engine plugin version 3.7.8 or earlier; per the CVSS vector (PR:N/UI:N) no authentication and no user interaction are needed against a default installation with the plugin active. The primary limiting factors are that the target site must have the AI Engine plugin installed and enabled at a vulnerable version, and impact is confined to reading data exposed via the affected IDOR-vulnerable object reference (C:L) - no write/integrity or availability compromise is possible. Successful data extraction may also depend on the attacker being able to guess or enumerate valid object identifiers. |
| Impact | The CVSS 3.1 vector (AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N, base 5.3, MEDIUM) describes a remotely reachable, unauthenticated, low-complexity flaw with no user interaction, but with impact limited to low confidentiality only (I:N/A:N) - consistent with CWE-639 IDOR that leaks specific objects rather than granting full compromise. No EPSS score, CISA KEV entry, SSVC decision data, or public POC is present in the provided intelligence, so there is no signal of active exploitation or automated weaponization; exploitation status is therefore 'no public exploit identified at time of analysis.' The realistic priority is moderate-to-low: unauthenticated network reach makes it opportunistically scannable, but the confined C:L impact (object/data disclosure, not takeover) and absence of KEV/EPSS evidence indicate this is a data-exposure hygiene issue rather than an urgent RCE-class emergency. Note the input Tag 'Authentication Bypass' conflicts with the CWE-639 classification, which is broken object-level authorization (IDOR), not authentication bypass - treat the tag as inaccurate. |
| Exploit ScenarioDerived | An unauthenticated attacker sends crafted requests to an AI Engine plugin endpoint, manipulating an object identifier (e.g., a numeric or predictable ID) to reference records they do not own. Because the endpoint fails to enforce object-level authorization, the attacker enumerates IDs to read data belonging to other users or the site. No public POC is referenced, and impact is limited to confidentiality disclosure (C:L) with no integrity or availability effect. |
Get an e-mail when this CVE is exploited, patched or re-scored. Free account.
Alert meAnalysisAIv1 – Sep 23, 2026
Unauthenticated insecure direct object reference (IDOR) in the WordPress plugin AI Engine at version 3.7.8 and earlier allows any remote attacker who can reach the site to read plugin-managed objects by manipulating object references, with no authentication and no user interaction required, as reflected in the CVSS 3.1 vector (AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N, base 5.3 MEDIUM). Impact is deliberately narrow: only low confidentiality loss is possible, with integrity and availability explicitly unaffected, and successful extraction generally depends on the attacker being able to guess or enumerate valid object identifiers. Based on the available data there is no confirmed active exploitation (not listed in CISA KEV) and no public exploit code identified at time of analysis; the flaw was reported through Patchstack and tracked in the EU as EUVD-2026-85465. Sites are exposed only if the AI Engine plugin is installed, active, and running a version at or below 3.7.8.
RemediationAI
No vendor-released patch version is identified in the available data at time of analysis, so the immediate priority is to check the Patchstack advisory at https://patchstack.com/database/wordpress/plugin/ai-engine/vulnerability/wordpress-ai-engine-plugin-3-7-8-insecure-direct-object-references-idor-vulnerability?_s_id=cve for the maintainer's fixed release and upgrade to it as soon as it is published; if the plugin is not essential to the site, deactivating and removing it entirely eliminates the exposure, at the cost of losing all AI Engine functionality. Where the plugin must remain on 3.7.8 or earlier pending an update, apply Patchstack-style virtual patching or a WAF rule that blocks unauthenticated requests to the plugin's object-retrieval endpoints (typically the plugin's AJAX actions and REST routes) from users lacking a valid logged-in session - the trade-off is that legitimate front-end features relying on anonymous access to those endpoints will break, and WAF coverage must be tuned to the actual request signatures rather than a generic ruleset. Because exploitation requires the ability to supply or guess valid object identifiers, reducing identifier predictability and avoiding public disclosure of object IDs is a useful secondary control, but it is obfuscation rather than a fix and should not be treated as sufficient. Finally, review WordPress access logs for anomalous enumeration-style requests against AI Engine endpoints to determine whether any data was accessed before mitigation, since the confidentiality-only impact (C:L) means a successful attack would be invisible to integrity or availability monitoring.
Affected VersionsENISA
Affected Packages
Source: OSV (Open Source Vulnerabilities)
Affects your stack
Affects 1 package in euvd
Checking this CVE against your own stacks and servers is part of the Basic plan and up.
Technical ContextAI · show details
The root cause class is CWE-639, Authorization Bypass Through User-Controlled Key - the classic IDOR pattern in which an application accepts an attacker-supplied identifier for an object and retrieves it without verifying that the requesting principal is entitled to that object. In this case the affected component is the WordPress plugin AI Engine, identified by the CPE cpe:2.3:a:jordy_meow:ai_engine:*:*:*:*:*:*:*:* (vendor namespace jordy_meow), which is a widely used plugin that exposes AI-related endpoints and stored objects to the front end of a WordPress installation. The CVSS vector confirms the request path is network-reachable (AV:N), requires no privileges (PR:N) and no user interaction (UI:N) against a default installation with the plugin enabled, so the vulnerable object-lookup routine is reachable anonymously - typically via a plugin AJAX handler or REST route that fails to enforce capability checks or ownership validation on the key it receives. Because the scope is unchanged (S:U) and only confidentiality is impacted at a low level (C:L, I:N, A:N), the flaw leaks specific referenced objects rather than enabling write operations, privilege escalation, or full site compromise; practical exploitation value therefore depends on how much sensitive content the plugin stores in those objects and on how predictable or enumerable their identifiers are.
Know when Ai Engine gets its next vulnerability
- Watch products and get an email when something new is published
- Check this CVE against your own stack and servers
- Exploit and PoC references, threat intelligence from 22 sources
No credit card · 7-day full trial
Severity by source
AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N
Unauthenticated remote IDOR (PR:N/UI:N, AV:N/AC:L) leaking specific objects gives low confidentiality only, with no integrity or availability impact and no scope change.
Primary rating from Vendor (Patchstack).
CVSS VectorVendor: Patchstack
DescriptionCVE.org
Unauthenticated Insecure Direct Object References (IDOR) in AI Engine <= 3.7.8 versions.
Threat Intelligence Overview
NVD
CVE.org
EPSS
Vulnrichment
How this decision was reached
The engine reads each signal below and applies a fixed list of rules from top to bottom. The first rule that matches sets the recommended action – like a statement, every line is shown.
What every action level means
SSVC AssessmentENISA
Priority Score
Attack Technique
Authentication bypass attacks exploit flaws in the verification mechanisms that control access to systems and applications.
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
Exploit-DB