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.

Executive Summary

Technical Details

Mitigations

References

Additional Metadata

{
  "score": "5.3",
  "pubDate": "2026-09-12T06:16:28.430Z",
  "pubdate": "2026-09-12T06:16:28.430Z",
  "executiveSummary": "The WPBot WordPress plugin, in versions prior to 8.5.7, is susceptible to an unauthenticated API resource exhaustion vulnerability. This flaw stems from a lack of authorization and nonce verification on specific AJAX actions designed to facilitate communication with third-party AI providers.\nThe vulnerability allows remote, unauthenticated attackers to leverage the victim's server-side configuration, specifically their AI provider API keys, to execute arbitrary prompts. By bypassing security checks, malicious actors can force the target application to perform unauthorized API requests, leading to the rapid depletion of the site administrator's prepaid or metered AI service quotas.\nThe attack is characterized by its simplicity, requiring no prior authentication or administrative privileges to exploit. The primary risk implications include significant financial impact due to unauthorized consumption of paid services and potential abuse of the site’s credentials for malicious AI-generated content. Affected systems are those running versions of the WPBot plugin below 8.5.7. Organizations should prioritize patching to the latest version to enforce mandatory nonce validation and access control on the affected AJAX endpoints.",
  "technicalDetails": "The vulnerability is localized within the AJAX request handling logic of the WPBot plugin. Specifically, multiple AJAX actions responsible for relaying user prompts to configured AI service providers lack the necessary security headers and validation checks, such as WordPress nonces (wp_nonce_field), intended to prevent Cross-Site Request Forgery (CSRF) and unauthorized access.\nRoot Cause: The plugin’s backend handlers for these AJAX actions fail to implement the 'check_ajax_referer()' function or perform any form of capability verification (e.g., 'current_user_can()'). Consequently, the server blindly trusts incoming requests directed at these endpoints regardless of the sender's authentication status.\nExploitation Method: An attacker can craft a HTTP POST request to the WordPress 'admin-ajax.php' endpoint, specifying the vulnerable action as a parameter. By injecting arbitrary prompt data into the request body, the attacker forces the server to process the prompt using the API keys statically stored or configured in the plugin's settings. The application then automatically forwards this request to the external AI service provider.\nAttack Flow: 1. The attacker identifies the vulnerable AJAX action names within the plugin source code. 2. The attacker sends an unauthenticated POST request to 'wp-admin/admin-ajax.php' containing the malicious prompt and the targeted action parameter. 3. The plugin, failing to validate the request via nonces or session checks, invokes the internal function responsible for API integration. 4. The server-side code retrieves the configured API credentials and dispatches the payload to the third-party AI vendor. 5. The third-party service processes the request and deducts the associated costs from the site owner’s account balance.\nImpact: The exploitation results in unauthorized utilization of service quotas and financial loss. Furthermore, it creates a conduit for an attacker to interact with powerful AI models using the reputation and credentials of the compromised WordPress instance, potentially leading to content injection or abuse of the vendor's Terms of Service, which may result in the suspension of the site owner's API access.\nAffected Versions: WPBot versions < 8.5.7. The vulnerability is publicly exposed to any network entity capable of reaching the WordPress installation's AJAX interface."
}