CVE-2026-93529 Overview
CVE-2026-93529 is a broken access control vulnerability in the WordPress plugin WSP MCP – AI Agents Connector in versions up to and including 2.7.0. The flaw allows authenticated users with Contributor-level privileges to perform actions that should be restricted to higher-privileged roles. The issue is tracked as a missing authorization weakness [CWE-862].
The vulnerability affects integrity of data managed through the plugin. It does not require user interaction and is exploitable over the network by any authenticated account with at least Contributor permissions.
Critical Impact
Contributor-level accounts can bypass access controls in the WSP MCP AI Agents Connector plugin and modify resources beyond their authorized scope, undermining site integrity.
Affected Products
- WordPress plugin WSP MCP – AI Agents Connector versions <= 2.7.0
- WordPress sites running the affected plugin with Contributor or higher user accounts
- Deployments exposing the plugin's AI agent connector endpoints
Discovery Timeline
- 2026-09-23 - CVE-2026-93529 published to NVD
- 2026-09-23 - Last updated in NVD database
Technical Details for CVE-2026-93529
Vulnerability Analysis
The WSP MCP – AI Agents Connector plugin exposes functionality that lacks proper capability checks. An authenticated user assigned the Contributor role can invoke actions that should require Editor or Administrator privileges. The result is unauthorized modification of plugin-managed resources.
The vulnerability affects integrity only. Confidentiality and availability are not directly impacted according to the CVSS vector. Because Contributor accounts are commonly granted on multi-author WordPress sites, the practical exposure is broader than administrator-only flaws.
Root Cause
The root cause is missing authorization [CWE-862]. Plugin handlers do not verify that the requesting user has the required WordPress capability before performing sensitive operations. Authentication alone is treated as sufficient, which violates the principle of least privilege.
Attack Vector
An attacker first obtains or compromises a Contributor account on a WordPress site running the vulnerable plugin. The attacker then sends crafted requests to the affected plugin endpoints. Because the handlers omit capability checks, the requests succeed and modify data the user should not control. No user interaction from an administrator is required.
See the Patchstack Vulnerability Report for the vendor-tracked technical write-up.
Detection Methods for CVE-2026-93529
Indicators of Compromise
- Unexpected modifications to plugin configuration, AI agent connectors, or associated post metadata performed by Contributor-role users.
- Requests to WSP MCP – AI Agents Connector plugin endpoints originating from low-privileged accounts.
- New or altered AI agent integrations that were not provisioned by an administrator.
Detection Strategies
- Review WordPress audit logs for actions on plugin resources performed by users below Editor role.
- Correlate admin-ajax.php and REST API requests to plugin routes against the requesting user's WordPress capability.
- Compare plugin configuration state against a known-good baseline to identify unauthorized changes.
Monitoring Recommendations
- Enable a WordPress activity logging plugin and forward events to a centralized log platform.
- Alert on privilege-sensitive plugin actions taken by non-administrative accounts.
- Monitor for creation of new Contributor accounts followed by immediate access to plugin endpoints.
How to Mitigate CVE-2026-93529
Immediate Actions Required
- Update WSP MCP – AI Agents Connector to a version later than 2.7.0 once a fixed release is available from the vendor.
- Audit all Contributor and higher accounts and remove any that are unused or unrecognized.
- Rotate credentials for accounts that may have interacted with the plugin during the exposure window.
Patch Information
Refer to the Patchstack Vulnerability Report for the current status of the vendor fix and upgrade guidance. Apply the vendor-supplied patched version as soon as it is published.
Workarounds
- Deactivate the WSP MCP – AI Agents Connector plugin until a patched version is installed.
- Restrict Contributor role assignments and enforce strong authentication on all WordPress accounts.
- Place the WordPress admin and REST API surfaces behind a web application firewall that blocks unauthorized calls to the plugin's endpoints.
Disclaimer: This content was generated using AI. While we strive for accuracy, please verify critical information with official sources.