dbcve.org
Missing AuthorizationWeakness · CWE-862

CVE-2026-6803

MEDIUM · 5.3 CVSS v3.1 Published 2026-07-11
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
62/100
Remediation priority · Elevated
Remotely reachable No privileges Zero-click 6 weeks old

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 Missing Authorization in all versions up to, and including, 1.4.12. This is due to missing capability checks and nonce verification on AJAX actions registered under both wp_ajax_ and wp_ajax_nopriv_ hooks, as the base controller's getPermissions() returns an empty array and neither removeGroup nor clear are added to getNoncedMethods(), causing the authorization gate to unconditionally return true for these actions. This makes it possible for unauthenticated attackers to delete specific records by ID or delete all records from any module's database table by unauthenticated attackers.

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 versions up to 1.4.12 has a missing authorization vulnerability. AJAX actions are registered with wp_ajax_nopriv_ hooks allowing unauthenticated access, and the base controller's getPermissions() returns an empty array while removeGroup and clear methods aren't protected by getNoncedMethods(), causing the authorization check to always pass. This allows unauthenticated attackers to delete specific records or truncate any module's database table.

MitigationUpdate to version 1.4.13 or later which adds proper capability checks and nonce verification. Until then, disable the plugin or restrict AJAX endpoint access at the web server level.

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
None
Integrity
Low
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/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. Confirm plugin installation and version
    Navigate to WordPress Admin > Plugins and look for 'AI Chatbot & Workflow Automation by AIWU' or check the plugin directory wp-content/plugins/ for a folder containing 'aiwu' or 'ai-chatbot' and read the main PHP file header for the Version: field
    Affected if The plugin is installed and the version is 1.4.12 or lower
  2. Verify AJAX endpoint exposure
    Search the plugin's PHP files for 'wp_ajax_nopriv_' strings - these hooks register AJAX actions accessible to unauthenticated users. Check files in includes/ or controllers/ directories.
    Affected if Any AJAX action is registered with wp_ajax_nopriv_ hook, making it accessible without authentication
  3. Inspect base controller authorization logic
    Locate the base controller PHP file (commonly Base.php or Controller.php) and examine the getPermissions() method - look for a function that returns an empty array
    Affected if getPermissions() returns an empty array, bypassing capability checks entirely
  4. Check removeGroup and clear method protection
    Find the methods named 'removeGroup' and 'clear' within the controller classes and verify they do NOT call getNoncedMethods() or any nonce verification routine
    Affected if These methods lack nonce verification and capability checks, allowing unauthenticated deletion or table truncation

A user is affected if the AI Chatbot & Workflow Automation plugin versions up to 1.4.12 is installed and the vulnerable AJAX endpoints are exposed without authorization guards.

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 version 1.4.13 or later which adds proper capability checks and nonce verification. Until then, disable the plugin or restrict AJAX endpoint access at the web server level.

Recommended fix Moderate confidence

Version 1.4.13 or later of AI Chatbot & Workflow Automation by AIWU plugin

  1. Log in to WordPress admin dashboard
  2. Navigate to Plugins > Installed Plugins
  3. Locate 'AI Chatbot & Workflow Automation by AIWU' plugin
  4. Click 'Update Now' if an update is available, or manually download version 1.4.13 or later from the WordPress plugin repository and upload via Plugins > Add New > Upload Plugin
  5. Verify the updated version is 1.4.13 or higher after updating
  6. Test that the plugin functionality works as expected after the update

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

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

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-6803 — 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-6803 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