AI Engine – The Chatbot, AI Framework & MCP for WordPress <= 3.3.2 - Authenticated (Editor+) Arbitrary File Upload
Strategic Overview
- Status
- Patched in 3.3.3
- Affected Plugin
- AI Engine – The Chatbot, AI Framework & MCP for WordPress
- Affected Version
<= 3.3.2- CVSS
- 7.2High
- Weakness type
- CWE-434 · Unrestricted Upload of File with Dangerous Type
- CVE
CVE-2026-23802
At a glance
CVE-2026-23802 is a high-severity Unrestricted Upload of File with Dangerous Type vulnerability in the AI Engine WordPress plugin, affecting versions <= 3.3.2. It carries a CVSS score of 7.2 (reachable over the network; low attack complexity; high confidentiality, integrity, availability impact). Exploitation requires an authenticated account at Editor level or above. The issue is fixed in version 3.3.3; sites on affected versions should update now. Disclosed February 2026, reported by 0xd4rk5id3.
Vulnerability Overview
The AI Engine – The Chatbot, AI Framework & MCP for WordPress plugin for WordPress is vulnerable to arbitrary file uploads due to missing file type validation in all versions up to, and including, 3.3.2. This makes it possible for authenticated attackers, with Editor-level access and above, to upload arbitrary files on the affected site's server which may make remote code execution possible.
Technical Analysis
The vector marks this flaw as remotely reachable over the network, with low attack complexity — no special timing or configuration is needed, and no interaction from a victim user. A successful exploit has high impact on confidentiality, integrity, availability — full site compromise territory.
CWE-434: Unrestricted Upload of File with Dangerous Type
Reaching this weakness in AI Engine <= 3.3.2 takes an account at Editor level or above. An unrestricted file upload lets a caller store a file whose type or destination the application does not properly constrain.
If an uploaded file lands anywhere the server will execute, the flaw becomes remote code execution and the site should be treated as fully compromised. For AI Engine the fix is 3.3.3: builds <= 3.3.2 are affected, anything from 3.3.3 onward is not.
Remediation
Update to version 3.3.3, or a newer patched version
How does WordSec protect against this?
An attacker needs Editor access first, so the firewall sees the attempt as traffic from a logged-in account: WordSec's web application firewall inspects request payloads before WordPress loads them. Classes like this one can leave something behind, so the staged malware scanner is the second half: it looks for dropped files and modified code rather than for the request that created them. None of that substitutes for the fix: AI Engine 3.3.3 closes this, and updating the plugin is the step that ends it.
- Firewall
- Scanner
- Alerts
External References
Related records
Same weakness class
- 9.8CVE-2023-51409: AI Engine: ChatGPT Chatbot Arbitrary File Upload
CVE-2023-51409 - 9.1CVE-2024-34440: AI Engine: ChatGPT Chatbot Arbitrary File Upload
CVE-2024-34440 - 8.8CVE-2025-7847: AI Engine 2.9.3 - 2.9.4 Arbitrary File Upload
CVE-2025-7847 - 7.2CVE-2026-1400: AI Engine <= 3.3.2 Arbitrary File Upload
CVE-2026-1400
Other vulnerabilities in AI Engine – The Chatbot, AI Framework & MCP for WordPress
- 9.8CVE-2025-11749: AI Engine Info Exposure to Privilege Escalation
CVE-2025-11749 - 8.8CVE-2026-15988: AI Engine <= 3.6.5 CSRF to Privilege Escalation
CVE-2026-15988 - 8.8CVE-2026-8719: AI Engine 3.4.9 Privilege Escalation
CVE-2026-8719 - 8.8CVE-2025-5071: AI Engine 2.8.0 - 2.8.3 Insufficient Authorization
CVE-2025-5071 - 8.0CVE-2025-6238: AI Engine 2.8.4 Insecure OAuth Implementation
CVE-2025-6238 - 7.2CVE-2026-65545: AI Engine Stored XSS
CVE-2026-65545 - 7.2CVE-2026-12511: AI Engine <= 3.5.4 Arbitrary File Write
CVE-2026-12511 - 7.2CVE-2026-27407: AI Engine Privilege Escalation
CVE-2026-27407
Vulnerability data © Defiant, Inc., provided under the Wordfence Intelligence T&C