CVE-2024-0452 is a medium severity (CVSS 5.0) missing authorization flaw in the AI ChatBot plugin for WordPress, in all versions up to and including 5.3.4. Any logged in user, down to subscriber, can upload files to a linked OpenAI account through the openai_file_upload_callback function. Update the plugin.
What's affected
The AI ChatBot plugin for WordPress by QuantumCloud, all versions up to and including 5.3.4. The record's product entry is the free edition. The cause is a missing capability check on the openai_file_upload_callback function. Capability checks are how WordPress decides whether the current user is allowed to do something.
The record links a trunk changeset, 3089461, touching the OpenAI integration file. That points to a fix after 5.3.4, but we could not confirm which release number carries it, and the Wordfence entry did not load. Check the plugin changelog.
The weaknesses are CWE-862, missing authorization, and CWE-284, improper access control. The vector is CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:N/I:L/A:N: network, low complexity, low privileges, no user interaction, with a scope change and low integrity impact. The attacker needs a login, but the lowest WordPress role is enough. It is not on the CISA Known Exploited Vulnerabilities list.
How to check if you're exposed
Read the version of the AI ChatBot plugin in the dashboard plugin list, or use WP-CLI:
wp plugin get chatbot --field=version
The slug chatbot comes from the plugin repository path in the record's changeset link. Anything at 5.3.4 or older is in range.
Then consider who has accounts. If your site allows open registration, anyone can become a subscriber and reach the function. If registration is closed and accounts are few, the exposure is smaller. Check whether you have connected an OpenAI account to the plugin, because the flaw acts on that linked account.
What to do now
- Find the sites that run the AI ChatBot plugin.
- Update to a release later than 5.3.4 that includes the fix, and check the changelog to confirm it.
- If you cannot update, deactivate the plugin or turn off open user registration.
- Review the files in the linked OpenAI account for entries you did not add or remove.
- Consider whether the OpenAI key stored in the plugin has more reach than it needs, and restrict it where the provider allows.
Why it matters
The plugin lets the site act on an external account. When a handler skips the capability check, every user who can reach the site's request endpoint can use that connection. The effect here is that someone with a basic account can add files to your OpenAI account, which could affect what the bot answers or run up storage.
A medium score understates the issue for sites where a store of OpenAI files holds business content, such as documents the chatbot answers from. The fix in all such cases is a capability check before any action that changes data, which is a small code change.
Quick check
Do I need to be an administrator to use CVE-2024-0452?
No. The record says authenticated users with subscriber level access and above can do it.
Is there a confirmed fixed version?
Not from the sources we read. The record links a changeset after 5.3.4. Check the plugin changelog for the release number.
Sources
Last reviewed: 19 October 2026.
