CVE-2026-87918: WPBot WordPress Plugin Auth Bypass Flaw

CVE-2026-87918 Overview

The WPBot WordPress plugin before version 8.5.7 contains a broken access control flaw [CWE-284] in several AJAX actions. These endpoints relay user prompts to configured third-party AI providers. The plugin does not perform authorization checks or validate nonces on these actions. Unauthenticated attackers can invoke the endpoints and force the site to issue AI provider API calls using the site owner's configured API keys. The result is unauthorized consumption of paid API quota and potential financial impact on the site owner.

Critical Impact
Unauthenticated attackers can abuse vulnerable WPBot AJAX handlers to make third-party AI API calls at the site owner's expense, draining paid API credits and inflating billing.

Affected Products

WPBot WordPress plugin versions prior to 8.5.7
WordPress sites with WPBot AI integrations configured (OpenAI or other supported providers)
Any deployment exposing the vulnerable AJAX endpoints to unauthenticated visitors

Discovery Timeline

2026-09-12 - CVE-2026-87918 published to NVD
2026-09-14 - Last updated in NVD database

Technical Details for CVE-2026-87918

Vulnerability Analysis

WPBot exposes multiple WordPress AJAX actions that forward user-supplied prompts to configured AI providers such as OpenAI. The affected handlers omit both capability checks and WordPress nonce verification. As a result, requests to admin-ajax.php targeting these actions succeed without authentication or session context.

Because the plugin uses the site's stored provider API key to make outbound requests, every attacker request consumes billable tokens on the site owner's account. Attackers can script high-volume requests to inflate costs, exhaust rate limits, or degrade the availability of the AI integration for legitimate visitors. The confidentiality impact is limited to the AI provider responses returned to the attacker.

Root Cause

The root cause is missing authorization enforcement on privileged AJAX actions [CWE-284]. WordPress requires developers to explicitly call current_user_can() and check_ajax_referer() to gate AJAX handlers. WPBot registered several prompt-relay actions on the wp_ajax_nopriv_ hook without these checks, exposing paid API functionality to any anonymous caller.

Attack Vector

Exploitation requires only network access to the target WordPress site. An attacker sends crafted HTTP POST requests to /wp-admin/admin-ajax.php specifying the vulnerable WPBot action name and a prompt payload. The plugin forwards the prompt to the configured AI provider, returns the completion, and charges the request against the site owner's API key. No authentication, user interaction, or elevated privileges are required. See the WPScan Vulnerability Report for endpoint specifics.

Detection Methods for CVE-2026-87918

Indicators of Compromise

Elevated request volume to /wp-admin/admin-ajax.php with WPBot-specific action parameters originating from unauthenticated sessions.
Unexpected spikes in AI provider billing, token usage, or rate-limit errors reported by the configured provider dashboard.
Outbound traffic from the web host to AI provider API endpoints that does not correlate with legitimate visitor chat sessions.

Detection Strategies

Review web server access logs for repeated POST requests to admin-ajax.php with WPBot action names lacking a valid Cookie or referer.
Correlate AI provider usage reports with WordPress session activity to identify traffic that cannot be attributed to logged-in users.
Enable WordPress debug logging or a plugin audit trail to record invocations of WPBot AJAX handlers.

Monitoring Recommendations

Configure billing alerts and hard usage caps at the AI provider level to detect and contain abuse quickly.
Monitor for sustained bursts of anonymous requests to admin-ajax.php and rate-limit at the WAF or reverse proxy tier.
Track the WPBot plugin version across the WordPress estate and alert on hosts still running versions prior to 8.5.7.

How to Mitigate CVE-2026-87918

Immediate Actions Required

Update the WPBot plugin to version 8.5.7 or later on every affected WordPress installation.
Rotate any AI provider API keys stored in the plugin configuration, since prior keys may have been abused.
Apply provider-side usage limits or spend caps to prevent runaway costs during and after remediation.

Patch Information

The vendor addressed CVE-2026-87918 in WPBot version 8.5.7 by adding authorization and nonce checks to the affected AJAX actions. Administrators should upgrade through the WordPress plugin repository or the site's plugin manager. Additional detail is available in the WPScan Vulnerability Report.

Workarounds

Deactivate the WPBot plugin until the update to 8.5.7 can be applied.
Block unauthenticated POST requests to admin-ajax.php with WPBot-specific action parameters at the WAF or reverse proxy.
Temporarily remove the configured AI provider API key from the plugin to neutralize the financial impact while planning the upgrade.

bash

# Example WAF rule concept - block anonymous WPBot AJAX actions
# Adjust the action name list to match the vulnerable handlers documented by WPScan
SecRule REQUEST_URI "@endsWith /wp-admin/admin-ajax.php" \
  "chain,deny,status:403,id:1008791,msg:'Block anonymous WPBot AJAX prompt relay'"
  SecRule ARGS:action "@rx ^(wpbot_[a-z_]+)$" \
    "chain"
    SecRule &REQUEST_COOKIES:wordpress_logged_in "@eq 0"