CVE-2026-87959 Overview
CVE-2026-87959 is a broken access control vulnerability in the WPBot WordPress plugin versions before 8.7.6. The plugin fails to perform a capability check on the AJAX action that saves its Claude AI provider settings. Authenticated users with subscriber-level access can overwrite these settings, including the API key used for the plugin's outgoing AI requests. This flaw is classified under [CWE-284] (Improper Access Control).
Critical Impact
Low-privileged subscribers can overwrite the Claude AI provider configuration and substitute the API key, redirecting AI traffic or disabling chatbot functionality on affected WordPress sites.
Affected Products
- WPBot WordPress plugin versions prior to 8.7.6
- WordPress installations exposing subscriber-level registration
- Sites integrating WPBot with the Anthropic Claude AI provider
Discovery Timeline
- 2026-09-16 - CVE-2026-87959 published to NVD
- 2026-09-17 - Last updated in NVD database
Technical Details for CVE-2026-87959
Vulnerability Analysis
The WPBot plugin registers an AJAX endpoint that persists Claude AI provider settings to the WordPress options table. The handler validates that the request originates from an authenticated session but omits a current_user_can() capability check. Any authenticated role, including subscriber, can invoke the action and modify configuration values.
The exposed settings include the Claude API key that the plugin uses for outgoing AI requests. An attacker with subscriber access can overwrite this key with an attacker-controlled value. Subsequent chatbot requests then route through the attacker's key, or fail entirely if the key is invalid.
Root Cause
The root cause is a missing authorization check in the AJAX save handler. WordPress requires plugin developers to combine nonce verification with a capability check such as current_user_can('manage_options'). WPBot enforces authentication only, treating any logged-in user as authorized to modify plugin-wide settings.
Attack Vector
Exploitation requires an authenticated account at the subscriber level, which many WordPress sites grant through open registration. The attacker sends a crafted POST request to the WordPress admin-ajax.php endpoint targeting the vulnerable action. The request body supplies replacement values for the Claude provider settings, and the server persists them without validating the caller's role.
No user interaction from an administrator is required. The impact is limited to configuration integrity and confidentiality of the stored API key, with no direct code execution path. See the WPScan Vulnerability Details for the technical write-up.
Detection Methods for CVE-2026-87959
Indicators of Compromise
- Unexpected changes to WPBot Claude provider settings in the WordPress wp_options table
- Outbound AI requests to Anthropic endpoints authenticated with an API key not owned by the site operator
- POST requests to admin-ajax.php referencing WPBot save actions originating from subscriber-level accounts
Detection Strategies
- Review WordPress access logs for admin-ajax.php requests carrying WPBot save-settings actions from non-administrative sessions
- Compare current WPBot option values against a known-good baseline to detect unauthorized modification of the Claude API key
- Alert on newly registered subscriber accounts that immediately issue POST requests to plugin AJAX endpoints
Monitoring Recommendations
- Enable WordPress audit logging for changes to plugin option records
- Monitor outbound network traffic from the web host to api.anthropic.com and correlate with the configured API key fingerprint
- Track WPBot billing or usage anomalies from the Anthropic account to identify unauthorized substitution
How to Mitigate CVE-2026-87959
Immediate Actions Required
- Update the WPBot WordPress plugin to version 8.7.6 or later on all affected sites
- Rotate the Claude API key stored in WPBot settings and revoke the prior key at the Anthropic console
- Audit existing subscriber accounts and remove any created during the exposure window
Patch Information
The vendor addressed the missing capability check in WPBot version 8.7.6. Administrators should apply the update through the WordPress plugin manager or by downloading the fixed release directly. Refer to the WPScan Vulnerability Details for advisory metadata.
Workarounds
- Disable the WPBot plugin until the patched version can be deployed
- Disable open user registration or restrict the default role to prevent unauthenticated visitors from obtaining subscriber accounts
- Use a web application firewall rule to block subscriber-level requests to WPBot AJAX save actions
# Configuration example: disable open registration and enforce minimum role
wp option update users_can_register 0
wp option update default_role subscriber
Disclaimer: This content was generated using AI. While we strive for accuracy, please verify critical information with official sources.
