CVE-2026-111372: AI ChatBot for WooCommerce <= 5.0.0 - Missing Authorization to Authenticated (Subscriber+) Arbitrary Modification via qcld_rag_manual_sync AJAX Action

Q: Who can exploit this issue?

Any authenticated WordPress user with subscriber-level access or higher can exploit it. The attacker does not need administrative privileges because the required wp_chatbot nonce is exposed to every authenticated frontend visitor.

Q: What does an attacker need to do to cause impact?

They need a valid authenticated account and must repeatedly invoke the qcld_rag_manual_sync AJAX action. The affected site must have an administrator-stored API key for OpenAI, Gemini, OpenRouter, or xAI that can be used for embedding requests.

Q: What is the practical impact of successful exploitation?

Attackers can trigger RAG document synchronization operations that make paid embedding API calls using the site administrator's stored AI-provider key. Repeated requests can consume API credits and create financial loss; the provided data does not indicate confidentiality or availability impact.

Q: Are default authenticated frontend users exposed to the nonce needed for exploitation?

Yes. The wp_chatbot nonce is emitted through wp_localize_script to every authenticated frontend visitor, so a subscriber account can obtain it without access to administrative pages.

Published Oct 28, 2026

Updated

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 wpchatbot nonce required to reach this endpoint is emitted to every authenticated frontend visitor via wplocalizescript, making it trivially obtainable by any subscriber-level account.

Affected Software

1 affected component

QuantumCloud AI ChatBot for WooCommerce – WoowBot<=5.0.0

Event History

Oct 28, 2026

CVE Published

via MITRE·06:45 AM

Data Sourced

via MITRE·06:45 AM

DescriptionSeverityWeakness

Frequently Asked Questions

Who can exploit this issue?

Any authenticated WordPress user with subscriber-level access or higher can exploit it. The attacker does not need administrative privileges because the required wp_chatbot nonce is exposed to every authenticated frontend visitor.

What does an attacker need to do to cause impact?

They need a valid authenticated account and must repeatedly invoke the qcld_rag_manual_sync AJAX action. The affected site must have an administrator-stored API key for OpenAI, Gemini, OpenRouter, or xAI that can be used for embedding requests.

What is the practical impact of successful exploitation?

Attackers can trigger RAG document synchronization operations that make paid embedding API calls using the site administrator's stored AI-provider key. Repeated requests can consume API credits and create financial loss; the provided data does not indicate confidentiality or availability impact.

Are default authenticated frontend users exposed to the nonce needed for exploitation?

Yes. The wp_chatbot nonce is emitted through wp_localize_script to every authenticated frontend visitor, so a subscriber account can obtain it without access to administrative pages.

CVE-2026-111372: AI ChatBot for WooCommerce <= 5.0.0 - Missing Authorization to Authenticated (Subscriber+) Arbitrary Modification via qcld_rag_manual_sync AJAX Action

Affected Software

Event History

Frequently Asked Questions

Who can exploit this issue?

What does an attacker need to do to cause impact?

What is the practical impact of successful exploitation?

Are default authenticated frontend users exposed to the nonce needed for exploitation?

Company

Resources

Contact

Frequently Asked Questions

Who can exploit this issue?

What does an attacker need to do to cause impact?

What is the practical impact of successful exploitation?

Are default authenticated frontend users exposed to the nonce needed for exploitation?