WPBot lets unauthenticated callers spend configured AI credits
WPBot before 8.5.7 exposes several AJAX actions that relay prompts to configured AI providers without authorization or nonce checks. An unauthenticated attacker can issue third-party API requests through the site and consume charges against its stored API keys. The authoritative export does not name the actions, prompt fields, providers, or rate limits.
- Component
- WPBot
- Plugin slug
wpbot- Affected
- < 8.5.7
- Safe version
8.5.7- Published
- Sep 12, 2026
This CVE was published Sep 12, 2026 and is one of 19 known issues for this plugin.
Update, patch or deactivate.
Update WPBot to 8.5.7 or later and audit provider usage and billing. Rotate API keys if abuse is suspected. The application-level fix must authorize each relay action, enforce request verification and server-side quotas, and never expose provider credentials to the caller.
A safe version is available, so updating to that version or later is the preferred remediation. If an immediate update is not practical, consider a targeted application patch or temporarily restricting the affected functionality.
Deactivate only when warranted by your risk profile, or when advised by your hosting provider in the limited circumstances where the vulnerability cannot otherwise be mitigated. If you’re unsure which action is appropriate, contact Fused or your hosting provider for guidance.
Technical description
The WPBot WordPress plugin before 8.5.7 does not perform any authorization or nonce check on several AJAX actions that relay prompts to its configured AI providers, allowing unauthenticated attackers to make those third-party API calls, and consume the associated cost, using the site's own configured API keys.
CVE / CNA vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N