Royal MCP at a glance
- 6 publicly disclosed vulnerabilities, 1 of them rated High or Critical. The most recent was disclosed on Oct 28, 2026.
- Ranked #1448 by popularity on WordPress.org (10,000+ active installs).
- The latest version is 2.0.0 (released Nov 17, 2026). The most recent security fix shipped in 1.5.10.
- Every disclosed vulnerability has a fix. If you are on the latest version, none of them apply to you.
- The first thing to do: update to the latest version and turn on automatic updates.
Check your Royal MCP version
Enter the Royal MCP version number shown on your Plugins screen to see only the vulnerabilities that apply to it, most serious first.
Your version number is compared on this page only. It is not sent anywhere.
Get an email when a new vulnerability is disclosed
We'll tell you when a new vulnerability is disclosed in “Royal MCP”, with the version that fixes it. Free, email address only, stop any time.
We use your email address only for these alerts. Privacy policy
Want every plugin and theme on your site checked daily?
With Security Ready Standard, just install the “KazLinks Security Ready” plugin from WordPress.org. It sends only the names and versions of your plugins and themes, and we check them against disclosed vulnerabilities every day. Your first in-depth scan is free.
How to check whether your site is affected
- 1
Find your version
In your WordPress dashboard, open Plugins → Installed Plugins and look at the version number under “Royal MCP”.
- 2
Compare it with the list below
If your version falls within “Affected versions”, that vulnerability applies to you. If you are on the “Fixed in” version or later, it does not.
- 3
Update
Click “Update now” to move to the latest version (2.0.0). Taking a backup first is a good idea.
- 4
Turn on automatic updates
On the same screen, click “Enable auto-updates” so future fixes are installed automatically.
Known Royal MCP vulnerabilities
Royal MCP – Secure AI Connector for Claude, ChatGPT & any LLM via MCP < 1.5.10 - Missing Authorization
Missing authorization · CVE-2026-111961
Affected versions: < 1.5.10
Fixed in: 1.5.10
Severity: Medium 4.3 · Disclosed Oct 28, 2026
Royal MCP – Secure AI Connector for Claude, ChatGPT & any LLM via MCP 1.4.38 - 1.5.9 - Missing Authorization
Missing authorization · CVE-2026-111960
Affected versions: ≥ 1.4.38, ≤ 1.5.9
Fixed in: 1.5.10
Severity: Medium 4.3 · Disclosed Oct 28, 2026
Royal MCP – Secure AI Connector for Claude, ChatGPT & any LLM via MCP < 1.5.7 - Authentication Bypass
Missing authorization · CVE-2026-111958
Affected versions: < 1.5.7
Fixed in: 1.5.7
Severity: High 7.5 · Disclosed Oct 20, 2026
Royal MCP – Secure AI Connector for Claude, ChatGPT & Gemini <= 1.4.25 - Missing Authorization
Missing authorization · CVE-2026-54842
Affected versions: ≤ 1.4.25
Fixed in: 1.4.26
Severity: Medium 4.3 · Disclosed Jun 18, 2026
Royal MCP <= 1.4.25 - Missing Authorization to Unauthenticated MCP Tool Use
Missing authorization · CVE-2026-10750
Affected versions: ≤ 1.4.25
Fixed in: 1.4.26
Severity: Medium 5.3 · Disclosed Jun 10, 2026
Royal MCP – Secure AI Connector for Claude, ChatGPT & Gemini <= 1.4.2 - Missing Authorization
Missing authorization · CVE-2026-40775
Affected versions: ≤ 1.4.2
Fixed in: 1.4.3
Severity: Medium 5.3 · Disclosed Apr 21, 2026
| Vulnerability | Affected versions | Fixed in | Severity | Disclosed |
|---|---|---|---|---|
| Royal MCP – Secure AI Connector for Claude, ChatGPT & any LLM via MCP < 1.5.10 - Missing AuthorizationMissing authorization · CVE-2026-111961 | < 1.5.10 | 1.5.10 | Medium 4.3 | Oct 28, 2026 |
| Royal MCP – Secure AI Connector for Claude, ChatGPT & any LLM via MCP 1.4.38 - 1.5.9 - Missing AuthorizationMissing authorization · CVE-2026-111960 | ≥ 1.4.38, ≤ 1.5.9 | 1.5.10 | Medium 4.3 | Oct 28, 2026 |
| Royal MCP – Secure AI Connector for Claude, ChatGPT & any LLM via MCP < 1.5.7 - Authentication BypassMissing authorization · CVE-2026-111958 | < 1.5.7 | 1.5.7 | High 7.5 | Oct 20, 2026 |
| Royal MCP – Secure AI Connector for Claude, ChatGPT & Gemini <= 1.4.25 - Missing AuthorizationMissing authorization · CVE-2026-54842 | ≤ 1.4.25 | 1.4.26 | Medium 4.3 | Jun 18, 2026 |
| Royal MCP <= 1.4.25 - Missing Authorization to Unauthenticated MCP Tool UseMissing authorization · CVE-2026-10750 | ≤ 1.4.25 | 1.4.26 | Medium 5.3 | Jun 10, 2026 |
| Royal MCP – Secure AI Connector for Claude, ChatGPT & Gemini <= 1.4.2 - Missing AuthorizationMissing authorization · CVE-2026-40775 | ≤ 1.4.2 | 1.4.3 | Medium 5.3 | Apr 21, 2026 |
Vulnerability data: Wordfence Intelligence (Copyright Defiant, Inc. · license terms). Severity is the CVSS score (0–10). Most recent disclosure: Oct 28, 2026.
Most common weaknesses in Royal MCP
Missing authorization
6 issues
Actions that should require a login or a particular role can be carried out without the proper check. Attackers use this to change settings or read data they should not see.
Frequently asked questions
Is Royal MCP safe to use?
Royal MCP is a well-known plugin with 10,000+ active installs. Finding vulnerabilities in popular plugins is common, and most of them are fixed in newer versions. The important thing is to stay on the latest version (2.0.0) and turn on automatic updates.
How do I find which version of Royal MCP my site is running?
In your WordPress dashboard, go to Plugins → Installed Plugins. The version number is shown under the plugin name. If you see “There is a new version available”, you are on an older version.
Could updating break my site?
Occasionally an update changes how something looks or works, so take a backup before updating. If an agency or developer maintains your site, send them a link to this page and ask them to update.
Can I check all my other plugins too?
Yes. Security Ready reads the versions of every plugin and theme on your site, matches them against known vulnerabilities every day, and tells you what to fix. Your first in-depth scan is free.
Check every plugin and theme automatically, every day
Security Ready reads the versions of every plugin, theme and WordPress core on your site, matches them against known vulnerabilities every day, and tells you how to fix what it finds. Your first in-depth scan is free, and no payment details are needed.
Think your site has already been hacked? Before updating, read what to do in the first hour. Updating alone does not remove a backdoor that has already been planted.