Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain
-
AccessAuthenticate as Editor-level user
-
ExploitCall media action with arbitrary post ID
-
ImpactPermanently delete protected site content
Vulnerability Assessment
| Weakness |
CWE
OWASP Top 10:2025
A01:2025 - Broken Access Control
ASVS 5.0
V8 - Authorization Authorization checks on every request
MITRE ATT&CK
1 technique across 1 tactic: Privilege Escalation The technique list with ATT&CK links and the kill-chain view is part of the Basic plan and up. |
| Exploitation Conditions | Requires an authenticated WordPress account with the Editor role or higher on a site running AI Engine before 3.7.9; the attacker then calls one of the plugin's media actions with the ID of an object they do not own. No special plugin configuration beyond having the vulnerable version active is described - the missing ownership/authorization check is present by default. Exploitation is strictly limited by the trusted-role requirement (Editor+), which prevents anonymous or low-privilege (Subscriber/Contributor) abuse and confines realistic risk to insider or compromised-account scenarios; no user interaction by a victim is needed. |
| Impact | This is a genuine but moderate-priority issue, not a critical internet-facing emergency. The CVSS 3.1 vector (CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:N/I:H/A:N, base 4.9) correctly captures the dominant limiting factor: exploitation requires an authenticated account with Editor role or above (PR:H/PR:L), so there is no path for an anonymous remote attacker. The CWE-862 (Missing Authorization) classification and description are consistent - this is a broken-access-control / insecure-direct-object-reference flaw, NOT an authentication bypass despite the misleading input tag. POC/exploit code is publicly available via WPScan, so weaponization is trivial once a sufficiently privileged account exists, but there is no CISA KEV listing and no EPSS score was supplied, so there is no evidence of active or widespread exploitation. Signals are internally consistent except for privilege level: the input vector uses PR:H, yet the description grants the capability to the Editor role, which is typically scored PR:L in WordPress - this discrepancy understates reach slightly (verify role mapping). Net: real-world risk is dominated by insider or compromised-privileged-account scenarios rather than mass exploitation, making this a timely-patch item rather than a drop-everything emergency. |
| Exploit ScenarioDerived | A disgruntled or compromised user holding an Editor account on a WordPress site running AI Engine < 3.7.9 invokes one of the plugin's media actions, supplying the ID of a post object they do not own. Because the plugin never verifies ownership before converting the item to an attachment and permanently deleting it, the attacker destroys protected content - navigation menus, block templates, or global styles - that their role should not be able to touch. Publicly available exploit code from WPScan lowers the effort required to carry this out. |
Get an e-mail when this CVE is exploited, patched or re-scored. Free account.
Alert meAnalysisAIv1 – Oct 18, 2026
AI Engine WordPress plugin before 3.7.9 allows authenticated users with the Editor role or higher to permanently delete arbitrary posts of any type by passing an object ID they do not own to a media action. The missing ownership/authorization check (CWE-862) lets such users remove navigation menus, block templates, global styles, and other content they cannot normally delete; publicly available exploit code exists. Exploitation requires an Editor+ account, which limits realistic exposure to insider or compromised-account scenarios and keeps this a moderate-priority issue rather than an anonymous internet-facing emergency.
RemediationAI
Upgrade AI Engine to 3.7.9 or later (vendor-released patch: 3.7.9) and confirm the update through the WPScan advisory at https://wpscan.com/vulnerability/c42eabbf-f357-46cd-b008-1b18eba83bf7/. If immediate upgrade is not possible, deactivate the plugin on sites where its AI/media features are not essential, accepting the loss of AI Engine functionality, or temporarily restrict Editor and higher roles to trusted accounts and remove unused Editor accounts, accepting reduced editorial capacity. Because exploitation requires Editor+, review role assignments and audit recent deletions of posts, navigation menus, block templates, and global styles, restoring affected content from backup where needed. Any attempt to block or filter the plugin's media action endpoint is not documented in the provided references, so validate such a rule against normal plugin behavior before deployment.
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 vulnerable code path is one of AI Engine's media actions: it converts a supplied item into an attachment and then permanently deletes it, but does not verify that the item belongs to the requesting user or that the user has delete permission for that specific object. This is CWE-862 Missing Authorization. In WordPress, posts of any type include navigation menu items, block templates, template parts, and global styles; Editors normally cannot delete all such objects, so the absent ownership check expands their destructive capability. The supplied CPE string cpe:2.3:a:unknown:ai_engine:*:*:*:*:*:*:*:* identifies the plugin but carries unknown vendor metadata in the provided data. The independent assessment records CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:H/A:N while the provided base vector lists PR:H; both remain consistent with the stated Editor-or-higher prerequisite and do not imply anonymous access.
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:H/UI:N/S:U/C:N/I:H/A:N
Editor role maps to PR:L (not PR:H); network-reachable action with low complexity and no UI; permanent deletion of protected content is a high integrity impact with no confidentiality effect.
Primary rating from Vendor (WPScan).
CVSS VectorVendor: WPScan
Lifecycle Timeline
3DescriptionCVE.org
The AI Engine WordPress plugin before 3.7.9 does not check that the item passed to one of its media actions belongs to the requesting user before converting it to an attachment and permanently deleting it, allowing users with the Editor role and above to delete arbitrary posts of any type, including content they cannot otherwise delete such as navigation menus, block templates and global styles.
Threat Intelligence Overview
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
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
EUVD-2026-103398
GHSA-8w27-j698-c24m
NVD
CVE.org
EPSS
Vulnrichment
VulDB
Exploit-DB