dbcve.org
SQL InjectionWeakness · CWE-89

CVE-2026-2993

HIGH · 7.5 CVSS v3.1 Published 2026-05-12
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
84/100
Remediation priority · High
Remotely reachable No privileges Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
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.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

The AI Chatbot & Workflow Automation by AIWU WordPress plugin has a SQL Injection vulnerability in the getListForTbl() function. The flaw stems from insufficient escaping of user-supplied parameters combined with lack of prepared statements in the SQL query, allowing unauthenticated attackers to inject and append malicious SQL queries to extract sensitive database information.

MitigationUpdate to the latest version of the plugin immediately. Although version 1.4.11 introduced a nonce check, it only protects authenticated administrators, leaving unauthenticated attackers still vulnerable.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
None
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Verify AIWU plugin is installed
    Check WordPress plugins directory for 'AI Chatbot & Workflow Automation by AIWU' folder in wp-content/plugins, or view installed plugins in WordPress admin dashboard
    Affected if plugin folder or entry exists in WordPress plugins list
  2. Identify installed plugin version
    Open the main plugin file (e.g., ai-chatbot-workflow-automation.php) and locate the Version header in the plugin comment block, or check in WordPress admin under Plugins > Installed Plugins
    Affected if version is lower than 1.4.11 or cannot be determined (unknown versions should be treated as vulnerable)
  3. Confirm vulnerable function is accessible
    Check if the plugin registers AJAX actions (via add_action for wp_ajax_ and wp_ajax_nopriv_) that call getListForTbl(), typically in the main plugin file or included class files; look for hooks like 'wp_ajax_getListForTbl' or 'wp_ajax_nopriv_getListForTbl'
    Affected if AJAX endpoint exposing getListForTbl is registered with nopriv (unauthenticated) access
  4. Test for unauthenticated SQL injection
    If available, send a crafted GET or POST request to admin-ajax.php with action=getListForTbl and a test parameter (e.g., parameter used in the function) containing a SQL payload like a single quote or UNION-based test; observe if SQL errors are returned or unexpected data behavior occurs
    Affected if SQL syntax errors appear in response or timing-based blind injection produces results confirming unsanitized input execution

If the AI Chatbot & Workflow Automation plugin is installed with a version below 1.4.11 AND the getListForTbl function is exposed to unauthenticated users via AJAX, the environment is vulnerable to CVE-2026-2993 SQL injection.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Update to the latest version of the plugin immediately. Although version 1.4.11 introduced a nonce check, it only protects authenticated administrators, leaving unauthenticated attackers still vulnerable.

Recommended fix Moderate confidence

1.4.18 or later

  1. 1. Navigate to the WordPress admin dashboard
  2. 2. Go to Plugins > Installed Plugins
  3. 3. Locate the 'AI Chatbot & Workflow Automation by AIWU' plugin
  4. 4. If an update is available, click 'Update Now' to update to the latest version
  5. 5. Alternatively, download the latest version from the WordPress plugin repository and upload it manually
  6. 6. After updating, verify the plugin is running version 1.4.18 or higher

Generated from the published advisory — verify against the referenced sources before acting.

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation1.0 h
  • Testing2.0 h
  • Review / QA1.0 h
6.0 hours of engineering $1,060
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,696.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-2993 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-2993 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data