Royal MCP CVE-2026-111960

Requires an authenticated WordPress account of any role, explicitly including subscriber-level (PR:L confirmed), and the vulnerable Royal MCP plugin installed at a version in the range 1.4.38 up to (not including) 1.5.10 with its search tool reachable; the disclosure of personal data specifically requires the companion Royal MCP plugin to be present and holding such data. Exploitation is limited by the authentication requirement - most impactful on sites that permit open/self-service user registration, where obtaining a subscriber account is trivial - and is bounded to read-only disclosure of entry titles and content (no write, modification, or denial of service). The trigger beyond 'the search tool lacks authorization checks' is not further detailed in the available sources.

This is a genuine-but-moderate issue, not a top-tier emergency, and the signals are internally consistent. The CVSS 3.1 vector (AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:N, base 4.3 Medium) describes a remotely reachable, low-complexity authorization flaw that requires an authenticated low-privileged account (PR:L) and yields only limited confidentiality impact (C:L) with no integrity or availability effect. EPSS is very low at 0.15% (4th percentile), the CVE is NOT on CISA KEV, and no public exploit is identified in the supplied data, so there is no evidence of active or widespread exploitation - consistent with an information-disclosure bug in a niche plugin rather than a mass-exploited RCE. The vuln.today decision label is 'this_month', indicating a routine-but-scheduled remediation priority rather than act_now/emergency. The one caveat is impact scope: the description says the disclosed data includes 'personal data', which can carry privacy/regulatory weight beyond what the C:L rating alone implies, so sites storing sensitive subscriber data should weight this higher than the raw 4.3 suggests. Authentication is confirmed required from the vector (PR:L); on sites that allow open user registration, that barrier is effectively trivial for an attacker to satisfy.

An attacker registers or already holds a low-privileged WordPress account (e.g. a subscriber) on a site running Royal MCP below 1.5.10, then invokes the plugin's search tool, which fails to enforce object-level or post-type authorization. The response returns the titles and content of non-public entries - including personal data held by the companion Royal MCP plugin - that the subscriber should not be able to see. No public exploit code is identified in the available data, and exploitation requires an authenticated account but no user interaction and only low complexity.