WordPress MCP Server for WordPress plugin <= 2.0.1 - Privilege Escalation vulnerability

published 2026-11-09 7h ago modified 2026-11-09 5h ago also EUVD-2026-120118

cvss: 8.8; version 3.1, CNA
cisa kev: Not listed; not in CISA's catalog
epss: —; no EPSS score yet
public exploits: 0; none known

Incorrect Privilege Assignment vulnerability in AtlasAiDev MCP Server for WordPress ai-workflow-automation-ai-agent-hub allows Privilege Escalation.This issue affects MCP Server for WordPress: from n/a through 2.0.1.

Patch / fix

fixed in 1

AtlasAiDev MCP Server for WordPress 2.0.2

Is CVE-2026-121576 in your stack? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.

Check with Fencer

CISA SSVC

Exploitation: none
Automatable: no
Technical impact: total
Assessed: 6h ago (2026-11-09)

CVSS scores

assigned by	version	score	vector
CNA	3.1	8.8	CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H

Affected products

AtlasAiDev MCP Server for WordPress

Classification

Weakness

CWE-266 Incorrect Privilege Assignment

Technology feeds

WordPress rss critical rss

References

patchstack.com /database/wordpress/plugin/ai-workflow-automation-ai-agent-hub/vulnerability/wordpress-mcp-server-for-wordpres
vdb-entry

Sources

CVE List CVE-2026-121576
NVD CVE-2026-121576

Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.