The MCP Server for WordPress WordPress plugin before 1.8.2 does not perform an object-level authorization check on one
Source GCVE Database
Not known to be exploited · CVSS 2.7 Low : upgrade to 1.8.2 when convenient.
Data as of 9 Nov 2026, 23:24 UTC
- EPSS
- 0.1% chance of exploitation in 30 days – higher than 7% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
- Patch
- Available – fixed in 1.8.2
CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:L/I:N/A:NExploitation evidence
Disclosed: evidence found.
CVE published 26 Sep 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: 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 9 Nov 2026.
What to do
Upgrade MCP Server for WordPress to 1.8.2.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| MCP Server for WordPress | Affected
| Fixed in
|
AI-suggested
A fix is available in MCP Server for WordPress plugin version 1.8.2 and later. Users should upgrade to version 1.8.2 or newer to address this vulnerability. No other mitigation guidance is provided or necessary.
Description
The MCP Server for WordPress WordPress plugin before 1.8.2 does not perform an object-level authorization check on one of its workflow REST routes, allowing users with the Contributor role to disclose the title and publication status of any post, page or custom post type, including other users' private, draft, pending and scheduled content.