Live › vulnerability › CVE-2026-111372
Go to dashboardThe AI ChatBot for WooCommerce (WoowBot) WordPress plugin, up to and including 5.0.0, fails to check authorization on its RAG document sync action. Any logged-in subscriber can repeatedly trigger embedding API calls billed to the site administrator's stored OpenAI, Gemini, OpenRouter or xAI key, draining AI credits.
Summary written from the sources below. Check the originals before acting.
First seen by InfraStack 2026-10-28 07:31 UTC. All times on this page are UTC.
Sites running the AI ChatBot for WooCommerce (WoowBot) plugin at version 5.0.0 or earlier that allow logins with subscriber-level accounts. The nonce needed for the attack is exposed to every authenticated visitor, so any open registration path is a risk. Sites without this plugin, or with it removed, can skip it.
No product ranges from the sources yet.
5.0.0 and below are affected.5.0.0 once a patched release is available; the sources do not name the fixed version.Each row is the first time that source carried this signal. The analyst’s rows are its own findings.
The AI ChatBot for WooCommerce – WoowBot plugin for WordPress is vulnerable to authorization bypass in all versions up to, and including, 5.0.0. This is due to the plugin not properly verifying that a user is authorized to perform an action. This makes it possible for authenticated attackers, with subscriber-level access and above, to repeatedly trigger RAG document sync operations that issue paid embedding API calls to OpenAI, Gemini, OpenRouter, or xAI charged to the site administrator's stored API key, draining their AI API credits and causing financial loss. The wp_chatbot nonce required to reach this endpoint is emitted to every authenticated frontend visitor via wp_localize_script, making it trivially obtainable by any subscriber-level account.
This page as .md · .json · in your agent: get_signal("CVE-2026-111372")
NVD data is provided by NIST and is public domain. Posts quoted belong to their authors.