Skip to main content
VulnerabilityPublished

CVE-2026-96526: MCP Server for WordPress · Information Exposure

Affects MCP Server for WordPressSource CVE Database V5

0
Compare

Not known to be exploited · CVSS 2.7 Low : upgrade to 1.8.2 when convenient.

Data as of 8 Nov 2026, 23:24 UTC

CVSS 3.1 base score
2.7Low
How severe the flaw is on the 0–10 CVSS scale.
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.
CISA SSVC
Exploitation
No evidence of active exploitation and no public proof of concept
Automatable
Attackers cannot reliably automate steps 1–4 of the kill chain
Technical impact
Limited control over the software or limited information exposure

CISA SSVC assessment, 2026-09-26.

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:N

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 26 Sep 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq 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

ProductAffectedFixed in
MCP Server for WordPressAffected
  • <1.8.2
Fixed in
  • 1.8.2

AI-suggested

A fixed version 1.8.2 of the MCP Server for WordPress plugin is available that addresses this vulnerability by implementing proper object-level authorization checks. Users should upgrade to version 1.8.2 or later to remediate this issue.

Description

CVE-2026-96526 is an information exposure vulnerability in the MCP Server for WordPress plugin versions before 1.8.2. It allows users with the Contributor role to access the title and publication status of any post, page, or custom post type, including private, draft, pending, and scheduled content, without proper authorization checks.

References

Community reviews

Loading reviews…