dbcve.org
Cross-site Scripting (XSS)Weakness · CWE-79

CVE-2026-2955

MEDIUM · 6.4 CVSS v3.1 Published 2026-05-20
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
70/100
Remediation priority · Elevated
Remotely reachable 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 Stored Cross-Site Scripting via the 'X-Forwarded-For' header in versions up to, and including, 1.4.14 due to insufficient input sanitization and output escaping. This makes it possible for unauthenticated attackers to inject arbitrary web scripts in pages that will execute whenever a user accesses an injected page. NOTE: Practical exploitation is constrained due to a 20-character storage limit.

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 fails to sanitize the X-Forwarded-For HTTP header before storing it in the database and fails to escape the stored value when rendering it in pages. This allows unauthenticated attackers to inject persistent malicious JavaScript through a crafted X-Forwarded-For header, which executes when users view affected pages.

MitigationUpdate the plugin to version 1.4.15 or later which includes proper input sanitization for the X-Forwarded-For header and output escaping. As a temporary mitigation, consider disabling the plugin or implementing WAF rules to filter malicious header values.

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
Low
User interaction
None
Scope
Changed
Confidentiality
Low
Integrity
Low
Availability
None

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:L/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 AIWU plugin is installed
    Navigate to WordPress admin dashboard > Plugins, or inspect the wp-content/plugins/ directory for a folder containing 'aiwu', 'chatbot', or 'ai-chatbot' in the name
    Affected if The AI Chatbot & Workflow Automation plugin is present in the WordPress installation
  2. Identify installed plugin version
    In WordPress admin, go to Plugins > Installed Plugins > AI Chatbot & Workflow Automation, and note the version number displayed; alternatively, check the main plugin PHP file for the 'Version' header in the plugin comment block
    Affected if Version is less than 1.4.14 (vulnerable versions)
  3. Verify X-Forwarded-For header handling exists
    Inspect the plugin source code (likely in the main PHP file or a handler file) for code that reads the X-Forwarded-For HTTP header using $_SERVER['X-Forwarded-For'] or a similar server variable
    Affected if The plugin code processes the X-Forwarded-For header without sanitization functions like sanitize_text_field
  4. Confirm lack of output escaping
    Search the plugin code for where the X-Forwarded-For value is output (e.g., in admin pages, frontend display, or logs); verify that esc_html() or esc_attr() is NOT used around this output
    Affected if The X-Forwarded-For value is output without esc_html() or esc_attr() escaping
  5. Test for stored XSS (optional active check)
    Send a crafted request with X-Forwarded-For: <script>alert(1)</script> (20-char limit applies) to any page on the site, then visit pages where bot traffic or logs are displayed to see if the script executes
    Affected if The injected header value is stored and rendered without proper encoding

A user is affected if the AI Chatbot & Workflow Automation plugin is installed with a version prior to 1.4.14 and the plugin processes the X-Forwarded-For header for storage or display.

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 the plugin to version 1.4.15 or later which includes proper input sanitization for the X-Forwarded-For header and output escaping. As a temporary mitigation, consider disabling the plugin or implementing WAF rules to filter malicious header values.

Recommended fix Moderate confidence

Version higher than 1.4.14 (check wordpress.org for the latest stable release)

  1. Log in to the WordPress admin dashboard
  2. Navigate to Plugins > Installed Plugins
  3. Locate the 'AI Chatbot & Workflow Automation by AIWU' plugin
  4. Check the current version number to confirm it is 1.4.14 or lower
  5. Navigate to Plugins > Add New > Upload Plugin, or download the latest version from wordpress.org
  6. Upload and install the latest version of the plugin
  7. Verify the plugin has been updated to a version higher than 1.4.14
  8. Test that the plugin functionality remains operational 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
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA1.0 h
10.0 hours of engineering $1,750
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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