AIWU AI Chatbot EUVD-2026-31064

Exploitation requires that the AIWU AI Chatbot plugin is installed, active, and running version 1.4.14 or earlier on a WordPress site. The injection vector is the X-Forwarded-For HTTP header, which the plugin processes and stores without sanitization - this is a default code path, not a special configuration mode, meaning any site with the vulnerable plugin installed and serving pages processed by it is potentially exposed. The stored payload only executes when a subsequent user (victim) loads an affected page, introducing an implicit triggering dependency not reflected in the UI:N CVSS score. The critical limiting factor is the 20-character storage cap on the injected value, which prevents standard-length XSS payloads and requires attacker-side payload minimization. The CVSS vector specifies PR:L (low privileges required), but the description states unauthenticated exploitation is possible - this discrepancy is unresolved and defenders should treat the authentication requirement as unconfirmed until clarified by Wordfence or the vendor.

The NVD CVSS 3.1 score of 6.4 (Medium) reflects Changed Scope (S:C), indicating the vulnerability crosses the security boundary from the plugin context into the broader WordPress session context, which is appropriate for stored XSS. However, two notable discrepancies exist in the provided CVSS vector (AV:N/AC:L/PR:L/UI:N/S:C/C:L/I:L/A:N) that must be flagged: first, the vector specifies PR:L (Low Privileges Required), yet the vulnerability description explicitly states exploitation is possible by unauthenticated attackers - this contradiction should be verified with Wordfence or the vendor, as it materially affects the exploitability score. Second, UI:N (No User Interaction) is atypical for stored XSS, which inherently requires a victim to load the injected page - this may be a scoring artifact and deserves scrutiny. No EPSS score was provided in the input data, so probabilistic exploitation likelihood cannot be quantified. No CISA KEV listing exists and no POC has been identified, placing this squarely in the lower-priority tier absent other contextual factors. The 20-character storage limit is the single most significant real-world risk reducer: it forces attackers into creative payload minimization, making reliable exploitation considerably harder than a standard stored XSS.

An unauthenticated attacker (per the CVE description, despite the PR:L CVSS discrepancy) sends an HTTP request to a page handled by the AIWU plugin with a crafted X-Forwarded-For header containing a compact XSS payload of 20 characters or fewer - for example, a minimal event-handler injection or an external script loader using a short URL. The payload is persisted by the plugin and subsequently rendered unescaped to any WordPress user or visitor who loads the affected page, triggering script execution in their browser context and potentially allowing session cookie theft or account takeover. No public POC exists at time of analysis, but the attack concept is elementary for any researcher familiar with HTTP header injection in web applications.