Chatbot with ChatGPT <= 2.4.5 - Missing Authorization to Unauthenticated OpenAI API Key Exposure
Strategic Overview
- Status
- Patched in 2.4.6
- Affected Version
<= 2.4.5- CVSS
- 5.8Medium
- Weakness type
- CWE-862 · Missing Authorization
- CVE
CVE-2024-6845
At a glance
CVE-2024-6845 is a medium-severity Missing Authorization vulnerability in the AI Chatbot & Semantic Search WordPress plugin, affecting versions <= 2.4.5. It carries a CVSS score of 5.8 (reachable over the network; low attack complexity). Exploitation requires no authentication. The issue is fixed in version 2.4.6; sites on affected versions should update now. Disclosed September 2024, reported by Kieran Burge.
Vulnerability Overview
The Chatbot with ChatGPT WordPress plugin for WordPress is vulnerable to unauthorized access of data due to a missing capability check on the wdgpt_retrieve_api_key() function in all versions up to, and including, 2.4.5. This makes it possible for unauthenticated attackers to retrieve an OpenAI key.
Technical Analysis
The vector marks this flaw as remotely reachable over the network, with low attack complexity — no special timing or configuration is needed, and no privileges on the target site, and no interaction from a victim user.
CWE-862: Missing Authorization
AI Chatbot & Semantic Search <= 2.4.5 carries this weakness at wdgpt_retrieve_api_key(), and reaching it takes no account at all. A missing authorization check means a function is reachable by anyone who can reach the endpoint, because the code never asks whether the caller is allowed to perform the action.
Any user who can reach the endpoint gets to run an action reserved for higher-privileged roles, from reading protected data to changing settings or content. For AI Chatbot & Semantic Search the fix is 2.4.6: builds <= 2.4.5 are affected, anything from 2.4.6 onward is not.
Remediation
Update to version 2.4.6, or a newer patched version
How does WordSec protect against this?
This one needs no account at all, which puts it outside what login hardening can reach; WordSec's login security narrows the account-level paths around it, and the firewall is what inspects the request itself. None of that substitutes for the fix: AI Chatbot & Semantic Search 2.4.6 closes this, and updating the plugin is the step that ends it.
- Login Security
- Alerts
External References
Related records
Same weakness class
Other vulnerabilities in AI Chatbot & Semantic Search: ChatGPT Answers From Your Content
Vulnerability data © Defiant, Inc., provided under the Wordfence Intelligence T&C