# CVE-2026-111961: The Royal MCP WordPress plugin before 1.5.10 does not perform an object-level permission check before duplicating a requested page, relying


- **Severity:** Low 3.8 (`CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:L/I:L/A:N`)
- **Exploited in the wild:** Not known
- **Fix available:** No
- **Published:** 28 Oct 2026
- **Updated:** 28 Oct 2026
- **Also known as:** GHSA-94r9-pgqm-7rh9

## What is CVE-2026-111961?

CVE-2026-111961 is a low-severity vulnerability in Unknown Royal MCP, published on 28 Oct 2026. 

### Official description

The Royal MCP  WordPress plugin before 1.5.10 does not perform an object-level permission check before duplicating a requested page, relying on a generic capability, which allows users with contributor-level access to read the full content of any private or draft page and to publish it without holding the publish capability.

Weakness: CWE-639 (Authorization Bypass Through User-Controlled Key)

## Which versions are affected by CVE-2026-111961?


## How do I fix CVE-2026-111961?

No fix has been published for CVE-2026-111961 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-111961 being exploited?

There is no known exploitation of CVE-2026-111961 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-111961 and fix it if it is affected.

What it is: CVE-2026-111961 is a low-severity vulnerability in Unknown Royal MCP, published on 28 Oct 2026. 
Exploitation: There is no known exploitation of CVE-2026-111961 in the wild and no public exploit code.

Affected product: Unknown Royal MCP. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-111961/ (Markdown: https://insights.sbomify.com/CVE-2026-111961/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-111961
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-111961
- OSV: https://osv.dev/vulnerability/CVE-2026-111961

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-111961/
Summaries are generated and may contain mistakes; the official description above is the record.