dbcve.org
VulnerabilityAwaiting classification

CVE-2026-10750

HIGH · 8.1 CVSS v3.1 Published 2026-07-01
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
87/100
Remediation priority · High
Remotely reachable Zero-click 8 weeks old

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
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.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

The Royal MCP WordPress plugin before 1.4.26 performs token-based authentication but fails to enforce capability checks on the majority of its MCP tool endpoints, creating a broken access control vulnerability that allows authenticated low-privileged users (Subscriber role) to read private content, enumerate all WordPress users and roles, and perform CRUD operations on content owned by other users.

MitigationUpdate the Royal MCP plugin to version 1.4.26 or later, which implements proper capability checks on MCP tool handlers. If immediate update is not possible, disable the plugin or restrict token authentication to administrative users only.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
None

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

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Identify Royal MCP plugin installation and version
    In WordPress admin, go to Plugins > Installed Plugins and locate Royal MCP plugin. Note the installed version number displayed next to the plugin name. Alternatively, check the plugin header in the main plugin file (commonly at wp-content/plugins/royal-mcp/royal-mcp.php) for the Version field.
    Affected if The installed version is lower than 1.4.26 or the version field cannot be determined (plugin may be present but unversioned).
  2. Confirm plugin is active
    In WordPress admin under Plugins > Installed Plugins, verify that Royal MCP shows as 'Active' rather than 'Inactive' or 'Must Use'. Only an active plugin can expose the vulnerable MCP endpoints.
    Affected if The plugin is active and the version is below 1.4.26.
  3. Check for exposed MCP API endpoints
    Probe common MCP endpoint paths on your site such as /wp-json/royal-mcp/v1/, /?rest_route=/royal-mcp/v1/, or /?action=royal_mcp_api. Use a browser or curl to request these paths and observe whether the server returns JSON API responses rather than a 404 error.
    Affected if MCP endpoints return API responses (even if requiring authentication), indicating the feature is enabled and potentially accessible to low-privilege users.
  4. Verify token-based authentication is configured
    Check the plugin settings page in WordPress admin (Royal MCP settings) to see if an API token or MCP token has been generated and enabled. Look for fields labeled API Token, MCP Token, Authentication Token, or similar in the plugin configuration.
    Affected if Token-based authentication is enabled, which is the authentication mechanism that bypasses the missing capability checks in affected versions.
  5. Test authorization enforcement on MCP tools
    Using a WordPress account with Subscriber role (the minimum privileged role), authenticate via the MCP token and attempt to access private posts (/wp-json/wp/v2/posts?status=private), list all users (/wp-json/wp/v2/users), or modify another user's content. Compare results against what a Subscriber should normally be able to access.
    Affected if A Subscriber-level account can read private content, enumerate users/roles, or modify other users' content through MCP tools, confirming the authorization bypass is present.

A user is affected if the Royal MCP plugin is active, version is below 1.4.26, MCP endpoints are accessible, and low-privilege users can bypass authorization through the MCP API.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Update the Royal MCP plugin to version 1.4.26 or later, which implements proper capability checks on MCP tool handlers. If immediate update is not possible, disable the plugin or restrict token authentication to administrative users only.

Recommended fix High confidence

1.4.26

  1. Log in to the WordPress admin dashboard
  2. Navigate to Plugins > Installed Plugins
  3. Find the Royal MCP plugin in the list
  4. Click 'Update Now' if an update is available, or manually upload version 1.4.26
  5. Verify the plugin version shows 1.4.26 or later after updating
  6. Test that authenticated users with Subscriber role can no longer access higher-privileged content or perform administrative actions

Generated from the published advisory — verify against the referenced sources before acting.

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing2.0 h
  • Review / QA1.0 h
9.0 hours of engineering $1,600
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,560.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-10750 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-10750 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data