What is the CVSS score of CVE-2026-10750?

CVE-2026-10750 has a CVSS 3.1 base score of 8.1 (High). CVSS vector: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:N. EPSS exploitation probability: 0.2%.

Which versions of Royal MCP are affected by CVE-2026-10750?

The Royal MCP WordPress plugin (versions before 1.4.26) contains a privilege escalation vulnerability enabling low-privileged users such as content subscribers to access restricted administrative…. A patch is available.

Is there a public PoC exploit available for CVE-2026-10750?

Yes, a public proof-of-concept exploit is available for CVE-2026-10750. Prioritise patching immediately. EPSS: 0.2%.

How to fix or mitigate CVE-2026-10750?

Within 24 hours: identify all WordPress installations using Royal MCP plugin and document current versions; assess exposure to low-privileged users (subscribers, contributors). Within 7 days: update all affected installations to Royal MCP plugin version 1.4.26 or later, prioritizing sites with public-facing subscriber access. Within 30 days: conduct security audit of user access logs for suspicious administrative actions by low-privilege accounts; reset credentials for high-privilege accounts (Administrator, Editor).

Royal MCP CVE-2026-10750

EUVD-2026-40914 HIGH

2026-07-01 WPScan

GHSA-mggr-4wrj-4f4g

WordPress Information Disclosure Royal Mcp Unknown

8.1

CVSS 3.1 · Vendor: WPScan

Severity by source

Vendor (WPScan) PRIMARY

8.1 HIGH

AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:N

vuln.today AI

8.1 HIGH

Network-reachable MCP tools abusable by any authenticated low-priv (Subscriber) account, so AV:N/AC:L/PR:L/UI:N; high confidentiality and integrity but no direct availability impact.

3.1 AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:N

4.0 AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:H/VA:N/SC:N/SI:N/SA:N

Primary rating from Vendor (WPScan).

CVSS VectorVendor: WPScan

Attack Vector

Network

Attack Complexity

Low

Privileges Required

Low

User Interaction

None

Scope

Unchanged

Confidentiality

High

Integrity

High

Availability

None

Lifecycle Timeline

Analysis Generated

Jul 01, 2026 - 11:22 vuln.today

CVSS changed

Jul 01, 2026 - 11:22 NVD

8.1 (None) 8.1 (HIGH)

Patch available

Jul 01, 2026 - 08:01 EUVD

CVE Published

Jul 01, 2026 - 06:00 cve.org

UNKNOWN (no severity yet)

CVE Published

Jul 01, 2026 - 06:00 cve.org

HIGH 8.1

DescriptionCVE.org

The Royal MCP WordPress plugin before 1.4.26 does not perform capability checks on the majority of its MCP tools after token authentication, allowing authenticated users with a low-privileged role such as Subscriber to read private content, enumerate all users and their roles, and create, modify, or delete content owned by other users.

Articles & Coverage 1

News 16 New WordPress Vulnerabilities - 2 Critical, 14 High, 4 With POC Jul 02, 2026

AnalysisAI

Broken access control in the Royal MCP WordPress plugin before 1.4.26 lets any authenticated low-privileged user (e.g. Subscriber) invoke privileged MCP tools that skip capability checks after token authentication, exposing private content, full user/role enumeration, and create/modify/delete operations on other users' content. Reported by WPScan with a publicly available exploit and a vendor patch in 1.4.26; the CVSS 8.1 vector (PR:L) confirms authenticated but not administrative access is required. There is no public exploit identified as actively exploited - status is POC only, not CISA KEV.

Technical ContextAI

Royal MCP exposes a Model Context Protocol (MCP) tool interface inside WordPress, allowing AI clients to interact with site data via tool calls gated by token authentication. The root cause is a broken/missing authorization pattern: after the plugin validates the MCP token, it fails to re-check the acting WordPress user's capabilities (e.g. edit_others_posts, list_users, read_private_posts) on the majority of its tools. This is a classic CWE-862 (Missing Authorization) / CWE-285 (Improper Authorization) class flaw, where authentication is conflated with authorization - token possession is treated as sufficient regardless of the underlying WordPress role. The CPE cpe:2.3:a:unknown:royal_mcp is the only affected component; the vulnerability lives entirely in the plugin's tool-dispatch layer, not WordPress core.

RemediationAI

Vendor-released patch: upgrade the Royal MCP plugin to version 1.4.26 or later, which restores capability checks on the affected MCP tools; this is the primary and complete fix. Until the update can be applied, reduce exposure by disabling the Royal MCP plugin entirely if the MCP integration is not in active use, which stops all tool access at the cost of losing MCP functionality. If the plugin must remain active, revoke or rotate MCP tokens and restrict which accounts hold them, tighten WordPress registration to prevent untrusted users from obtaining Subscriber accounts (disable open self-registration), and where possible block or IP-restrict the MCP endpoint so only trusted clients can reach it - noting this breaks legitimate remote MCP clients. Refer to the WPScan advisory (https://wpscan.com/vulnerability/8678ef91-ff05-43a1-a8e3-6d35da548826/) for confirmation of the fixed version.