CVE-2026-111960VulnerabilityPublished 28 Oct 2026

The Royal MCP WordPress plugin before 1.5.10 does not perform object-level or post-type authorisation checks in one of

Source GCVE Database

Authoritative record:CVE-2026-111960· High

Not known to be exploited : upgrade to 1.5.10 soon.

Data as of 28 Oct 2026, 07:27 UTC

Severity

High

Rated High by Threat Radar's AI analysis · CVSS not yet scored by NVD

Patch: Available – fixed in 1.5.10

Exploitation evidence

Disclosed: evidence found.
CVE published 28 Oct 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponised: Public exploit code exists in Metasploit or Exploit-DB, or CISA SSVC or the CVSS exploit maturity reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

ghsa-334j-cwwv-qmmh

What to do

Upgrade Royal MCP (WordPress plugin) to 1.5.10.

Affected software

Product	Affected	Fixed in
Royal MCP	Affected >=1.4.38 <1.5.10	Fixed in 1.5.10

AI-suggested

Upgrade the Royal MCP WordPress plugin to version 1.5.10 or later, where the authorization checks have been implemented to prevent unauthorized access to non-public entries. No other mitigation steps are indicated.

Description

The Royal MCP WordPress plugin versions before 1.5.10 lack proper object-level and post-type authorization checks in one of its search tools. This vulnerability allows authenticated users with low privileges, such as subscribers, to access the title and content of non-public entries, potentially exposing personal data stored by the plugin.

Impact

Authenticated users with subscriber-level privileges can disclose titles and content of non-public entries, including personal data stored by the plugin. This unauthorized data exposure can lead to privacy violations and information leakage within the affected WordPress site.

Summary

The Royal MCP WordPress plugin prior to version 1.5.10 contains an authorization flaw in a search tool that fails to enforce object-level or post-type access controls. As a result, authenticated users with minimal permissions can retrieve sensitive information from non-public posts, including personal data managed by the plugin. This issue arises from missing authorization checks that should restrict access based on user roles and post visibility.

References

Community reviews

Loading reviews…