WoowBot EUVD-2026-111744

Requires an authenticated WordPress account at subscriber-level or above (PR:L) on a site running AI ChatBot for WooCommerce - WoowBot ≤5.0.0 that has an administrator-configured paid AI provider API key (OpenAI, Gemini, OpenRouter, or xAI) enabling RAG document sync. The required wp_chatbot nonce is not a meaningful barrier because it is emitted to every authenticated frontend visitor via wp_localize_script. Limiting factors: the attacker must hold a logged-in account (so impact is far higher on stores permitting open customer/subscriber registration than on closed sites), and a paid AI key must actually be configured - without a configured provider key there is no billable action to abuse. No user interaction beyond the attacker's own requests is needed.

This is a genuine-but-moderate priority, not a high-severity emergency. The CVSS vector (AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:L/A:N, base 4.3) is internally consistent with the description: network-reachable, low complexity, but requiring authentication (PR:L). The only impact is integrity-low (unauthorized triggering of an action); there is no confidentiality or availability loss to the site itself - the actual harm is financial (draining the administrator's prepaid AI API credits at OpenAI/Gemini/OpenRouter/xAI). No EPSS score, KEV listing, or working PoC is present in the supplied data, so exploitation is no public exploit identified at time of analysis. The vuln.today decision label is this_month, consistent with a real-but-not-urgent authenticated authorization flaw. The main risk amplifier is that the required wp_chatbot nonce is emitted to every authenticated frontend visitor via wp_localize_script, so the PR:L barrier is only 'any logged-in subscriber' - low on sites that allow open/customer registration (common for WooCommerce stores). The main risk limiter is that there is no code execution, data theft, or site-availability impact; the worst outcome is monetary cost and possible AI-service disruption. Net: patch this month, prioritize sooner on stores with open customer registration and a configured paid AI key.

On a WooCommerce store running WoowBot ≤5.0.0 with an admin-configured AI provider key, an attacker registers (or uses) a subscriber-level account, loads any authenticated frontend page to harvest the wp_chatbot nonce leaked via wp_localize_script, and then repeatedly calls the unprotected RAG document-sync endpoint. Each call issues paid embedding API requests billed to the administrator's stored key, draining credits and causing financial loss. No public exploit code is identified in the supplied data, and the low attack complexity (AC:L) plus trivially obtainable nonce make scripted abuse straightforward for any logged-in user.