CVE-2026-10750 Overview
CVE-2026-10750 is a broken access control vulnerability in the Royal MCP WordPress plugin versions prior to 1.4.26. The plugin fails to enforce capability checks on the majority of its Model Context Protocol (MCP) tools after token authentication. Authenticated users holding low-privileged roles such as Subscriber can read private content, enumerate all users and their roles, and create, modify, or delete content owned by other users. The flaw enables horizontal and vertical privilege escalation against WordPress sites running the affected plugin.
Critical Impact
Authenticated low-privileged users can access private content and manipulate other users' posts, breaking the WordPress role-based access model.
Affected Products
- Royal MCP WordPress plugin versions prior to 1.4.26
- WordPress sites exposing the plugin's MCP tool endpoints
- Deployments granting Subscriber-level or higher accounts
Discovery Timeline
- 2026-07-01 - CVE-2026-10750 published to NVD
- 2026-07-01 - Last updated in NVD database
Technical Details for CVE-2026-10750
Vulnerability Analysis
The Royal MCP plugin exposes a set of MCP tools that operate on WordPress content and user data. After a request presents a valid authentication token, the plugin routes calls to the requested tool without verifying whether the calling user has the WordPress capability required for that action. This is a classic broken access control pattern where authentication is conflated with authorization. A Subscriber account, which normally has no rights beyond managing its own profile, can invoke tools that read, list, mutate, or delete arbitrary content. The vulnerability produces confidentiality and integrity impact but does not affect availability, per the CVSS vector.
Root Cause
The root cause is missing capability checks inside the MCP tool handlers. WordPress provides current_user_can() to gate privileged operations, but the affected handlers rely solely on token validation. Once the token is accepted, the code proceeds to execute actions such as reading private posts, listing users via get_users()-equivalent calls, and creating or deleting posts belonging to other authors without further authorization checks.
Attack Vector
An attacker registers or obtains a Subscriber-level account on a target WordPress site running Royal MCP prior to 1.4.26. The attacker authenticates to obtain a valid token, then issues MCP tool requests over HTTP to enumerate users, read private drafts, and modify or delete posts owned by administrators or editors. The attack is remote, requires low complexity, and needs no user interaction.
No public proof-of-concept code is available. Refer to the WPScan Vulnerability Details for the vendor-provided technical description.
Detection Methods for CVE-2026-10750
Indicators of Compromise
- Unexpected MCP tool requests originating from accounts with the Subscriber role in web server access logs.
- Posts modified, created, or deleted by user IDs that do not match the recorded post author.
- Bulk user enumeration responses returned to authenticated sessions belonging to low-privileged accounts.
Detection Strategies
- Audit WordPress access logs for requests to Royal MCP tool endpoints followed by content mutation events tied to non-author accounts.
- Correlate WordPress wp_posts and wp_users audit records with authentication logs to identify capability boundary violations.
- Alert on Subscriber-role sessions issuing sequential API calls that read or modify multiple resources across users.
Monitoring Recommendations
- Enable WordPress audit logging plugins to capture post creation, modification, deletion, and user enumeration events with actor identity.
- Forward web server and application logs to a centralized analytics platform for cross-user activity correlation.
- Track the installed version of Royal MCP across managed WordPress sites and alert on versions below 1.4.26.
How to Mitigate CVE-2026-10750
Immediate Actions Required
- Upgrade the Royal MCP plugin to version 1.4.26 or later on every WordPress instance.
- Review recent content changes and user enumeration activity for signs of abuse by low-privileged accounts.
- Rotate MCP authentication tokens after upgrading to invalidate any tokens issued to attackers.
Patch Information
The vendor addressed CVE-2026-10750 in Royal MCP version 1.4.26 by adding capability checks to the affected MCP tool handlers. See the WPScan Vulnerability Details for advisory information.
Workarounds
- Disable or uninstall the Royal MCP plugin until the upgrade to 1.4.26 can be applied.
- Restrict open user registration and remove unused Subscriber accounts to reduce the attacker pool.
- Place the WordPress admin and MCP endpoints behind IP allowlists or a web application firewall while patching is pending.
# Configuration example: verify installed Royal MCP version via WP-CLI
wp plugin get royal-mcp --field=version
wp plugin update royal-mcp --version=1.4.26
Disclaimer: This content was generated using AI. While we strive for accuracy, please verify critical information with official sources.
