EUVD-2026-29389
GHSA-8wr2-c6vh-58c4
Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain
-
AccessAccess WordPress AJAX endpoint
-
DeliveryInject SQL payload into getListForTbl() parameter
-
ExploitDatabase executes malicious UNION query
-
ExecutionExtract wp_users credentials and sensitive data
-
ImpactLeverage stolen admin credentials for persistent access
Vulnerability Assessment
| Weakness |
CWE
OWASP Top 10:2025
A05:2025 - Injection
ASVS 5.0
V1 - Encoding and Sanitization Parameterized queries, prepared statements
MITRE ATT&CK
2 techniques across 2 tactics: Initial Access, Persistence The technique list with ATT&CK links and the kill-chain view is part of the Basic plan and up. |
| Exploitation Conditions | Versions through 1.4.10: No special conditions required - remote unauthenticated exploitation against default WordPress installations with the AIWU chatbot plugin active. Any attacker with network access to the WordPress site can trigger the vulnerable getListForTbl() function through standard WordPress AJAX request mechanisms. Versions 1.4.11 through 1.4.17: Exploitation requires possession of a valid WordPress administrator nonce token, significantly limiting the attack to scenarios where the attacker has compromised an admin session, obtained the nonce through cross-site scripting, or convinced an administrator to visit a malicious page that harvests the nonce. The underlying SQL injection flaw remains exploitable once this authentication hurdle is cleared. Attack surface is expanded on sites where administrator users interact with untrusted content or third-party plugins that might leak nonces. The vulnerability does NOT require special chatbot configuration, specific AI model settings, or non-default WordPress database structures - it affects the core data retrieval layer used regardless of chatbot workflow setup. |
| Impact | Real-world risk assessment reveals moderate-to-high priority despite the 7.5 CVSS score. The CVSS vector (AV:N/AC:L/PR:N/UI:N) indicates trivially exploitable remote unauthenticated access with no user interaction required, which normally signals critical urgency. However, the partial mitigation in 1.4.11+ significantly reduces exploitability by requiring administrator-level nonce tokens for the affected endpoints. This transforms the attack from 'any internet attacker' to 'attacker who can obtain or bypass admin nonce' - a substantial defensive barrier. The Confidentiality:High/Integrity:None/Availability:None vector confirms this is purely a data exfiltration risk, not remote code execution. No EPSS score provided but absence from CISA KEV and lack of public exploit mentions suggest limited in-the-wild activity. Wordfence's detailed code-level disclosure increases POC development likelihood. Key risk factor: many WordPress sites run outdated plugin versions, and administrators may not understand that versions 1.4.11-1.4.17 remain vulnerable despite the nonce 'patch'. Sites using AIWU plugin in default configurations with versions ≤1.4.10 face immediate unauthenticated SQL injection risk. Sites on 1.4.11-1.4.17 have reduced but not eliminated risk. The scope is limited to installations of this specific plugin, not widespread WordPress core issue. |
| Exploit ScenarioDerived | An unauthenticated remote attacker identifies a WordPress site running AIWU chatbot plugin version 1.4.10 or earlier. They craft HTTP POST requests to WordPress AJAX endpoints that invoke the getListForTbl() function, injecting SQL UNION statements into unsanitized table name or column parameters. Through iterative UNION-based or blind SQL injection techniques, the attacker extracts wp_users table contents including administrator credentials (hashed passwords, email addresses), customer data from custom tables, or e-commerce transaction records if WooCommerce is integrated. For versions 1.4.11-1.4.17, the attacker must first obtain a valid administrator nonce token, possibly through social engineering, cross-site scripting in another plugin, or session hijacking. Once database contents are exfiltrated, the attacker uses cracked administrator credentials for site takeover or sells extracted customer data. The CVSS AC:L (low complexity) rating reflects the ease of crafting SQL injection payloads using standard penetration testing tools like sqlmap. |
Get an e-mail when this CVE is exploited, patched or re-scored. Free account.
Alert meAnalysisAIv1 – May 12, 2026
SQL injection in the AIWU AI Chatbot WordPress plugin (versions ≤1.4.17) allows remote unauthenticated attackers to extract sensitive database contents via the getListForTbl() function due to unsanitized user input in SQL queries. Partial mitigation exists in version 1.4.11+ through administrator-only nonce protection, but the underlying SQL injection vulnerability persists. CVSS 7.5 (High) reflects network-accessible unauthenticated exploitation with high confidentiality impact. Wordfence provides detailed vulnerable code references across multiple plugin files including controller.php, req.php, and model.php. No evidence of active exploitation (not in CISA KEV) at time of analysis.
RemediationAI
WordPress site administrators should immediately update the AIWU AI Chatbot plugin to a version beyond 1.4.17 that fully addresses the SQL injection vulnerability, once released by the vendor. As of this analysis, no fully patched version has been confirmed - the vendor's 1.4.11 release only adds nonce authentication, which mitigates but does not eliminate the underlying CWE-89 flaw. Monitor the WordPress plugin repository and Wordfence advisories for a complete security release. Until a proper fix is available, implement these compensating controls: (1) If the chatbot functionality is not business-critical, deactivate and uninstall the plugin entirely - this eliminates all attack surface. (2) If plugin must remain active, restrict wp-admin access to trusted IP addresses via web application firewall rules or .htaccess directives, reducing the attack surface for obtaining administrator nonces. Trade-off: this breaks legitimate remote admin access and may interfere with WordPress mobile apps. (3) Deploy a WordPress security plugin with virtual patching capabilities (e.g., Wordfence, Sucuri) that can filter malicious SQL patterns in HTTP requests. Trade-off: may cause false positives requiring tuning. (4) Enable WordPress database activity logging to detect SQL injection attempts via unusual query patterns. Review the specific vulnerable code locations in controller.php, req.php, and model.php referenced at https://plugins.trac.wordpress.org/browser/ai-copilot-content-generator/ to understand your exposure profile.
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
This is a classic SQL injection vulnerability (CWE-89) in a WordPress plugin's database query layer. The affected product 'AI Chatbot & Workflow Automation by AIWU' (CPE: cpe:2.3:a:wupsales:ai_chatbot_&_workflow_automation_by_aiwu) handles database operations through the getListForTbl() function in its model layer. The vulnerability stems from direct concatenation or interpolation of user-supplied HTTP parameters into SQL queries without proper escaping or use of prepared statements. WordPress provides $wpdb->prepare() for parameterized queries, but the plugin fails to use it consistently. The partial mitigation in 1.4.11 adds a WordPress nonce check that restricts access to certain admin endpoints, but this is authentication bypass prevention rather than input sanitization - the SQL injection payload can still execute if the nonce check is satisfied or bypassed. The references point to specific line numbers in controller.php (L104, L114, L132, L154, L157), req.php (L194), and model.php (L162) showing the vulnerable code patterns across the plugin architecture.
Know when Wordpress Plugin 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:H/I:N/A:N
Primary rating from NVD · only source for this CVE.
CVSS VectorNVD
DescriptionCVE.org
The AI Chatbot & Workflow Automation by AIWU plugin for WordPress is vulnerable to SQL Injection in versions up to, and including, 1.4.17 due to insufficient escaping on user supplied parameters and lack of sufficient preparation on the existing SQL query in the getListForTbl() function. This makes it possible for unauthenticated attackers to append additional SQL queries into already existing queries that can be used to extract sensitive information from the database. NOTE: This issue is partially mitigated by a patch in version 1.4.11 that adds a nonce check for a nonce that is only available to administrators.
Executive ViewAI
The AIWU AI Chatbot WordPress plugin (versions ≤1.4.17) contains an unauthenticated SQL injection vulnerability that allows attackers to extract sensitive database contents without credentials. Organizations using this plugin risk unauthorized access to customer data, credentials, and other confidential information stored in WordPress databases. Immediate assessment and remediation are critical given the plugin's direct database exposure and lack of vendor patch.
Immediate interim mitigations (pending vendor patch): (1) Disable or remove the vulnerable plugin entirely; (2) If plugin use is operationally critical, implement network-level access controls restricting plugin-related endpoints to authenticated administrative users only; (3) Enable Web Application Firewall (WAF) rules to detect and block SQL injection patterns targeting the identified vulnerable functions (getListForTbl, controller.php, req.php, model.php); (4) Implement database query logging and real-time alerting for suspicious SQL patterns; (5) Ensure database credentials follow least-privilege principles. None of these controls substitute for vendor patch application once available.
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
SQL injection exploits the way applications construct database queries by mixing user input directly into SQL statements.
More in Wordpress Plugin
View allThe Backup Migration plugin for WordPress is vulnerable to Remote Code Execution in all versions up to, and including, 1
The Hash Form - Drag & Drop Form Builder plugin for WordPress is vulnerable to arbitrary file uploads due to missing fil
Authentication bypass in the LiteSpeed Cache WordPress plugin (versions prior to 6.5.0.1) allows unauthenticated remote
The Simple File List plugin for WordPress through version 4.2.2 contains an unauthenticated remote code execution vulner
The AI Engine WordPress plugin through version 3.1.3 exposes Bearer Token values through the /mcp/v1/ REST API endpoint
The SureTriggers WordPress plugin through version 1.0.82 contains a privilege escalation vulnerability that allows unaut
The Ninja Forms plugin before 2.9.42.1 for WordPress allows remote attackers to conduct PHP object injection attacks via
The Business Directory Plugin - Easy Listing Directories for WordPress plugin for WordPress is vulnerable to time-based
SQL injection in the NotificationX WordPress plugin (versions up to and including 2.8.2) allows unauthenticated remote a
The POST SMTP Mailer - Email log, Delivery Failure Notifications and Best Mail SMTP for WordPress plugin for WordPress i
The MasterStudy LMS WordPress Plugin - for Online Courses and Education plugin for WordPress is vulnerable to union base
The Email Subscribers by Icegram Express plugin for WordPress is vulnerable to SQL Injection via the ‘hash’ parameter in
Exploit-DB