WordPress MCP Server for WordPress plugin <= 2.0.1 - Privilege Escalation vulnerability
Affects the MCP Server for WordPress plugin version 2.0.1 and earlier, where a low-privilege user can become an admin. Fixed in 2.0.2.
Written by anthropic/claude-haiku-5.5 from the sources below. Verify against them.
- Exploited
- No known exploitation
- Fix
- Fixed in 2.0.2
- Who is exposed
- Specific setups only
Do first: Check whether your setup matches what the bug needs. WordPress MCP Server for WordPress plugin version 2.0.1 or earlier
- Published
- Last modified
- A 0-100 score for how much a CVE matters across the industry: exploitation, exposure, how widely the software is used, severity and whether a fix exists.What do these mean? →
- 18/100 · provisional
- How many real-world setups can hit the bug, from the vendor's advisory and CISA data. It does not know your setup.What do these mean? →
- Specific setups only
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
- Exploitation: none
- Automatable: no
- Technical impact: total
Summary
The WordPress MCP Server for WordPress plugin, from AtlasAiDev, has a privilege escalation flaw caused by incorrect privilege assignment. An attacker who can reach the site over the network and has a low-privilege account can exploit it without any user interaction to gain higher privileges.
Read the original description
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.
cve.now Index
- Exploitation0/40No signal
- Exposure8/25Specific setups only, reachable over the network
- Reach?/20Unknown. No tracked technology or package matched
- Severity9.8/10CVSS 8.8, total technical impact per CISA
- No patch0/5No signal
What would change the score
- Would score about 68 if added to CISA KEV
- Would score about 63 if CISA's SSVC rates exploitation active
- Would score about 25 if CISA's SSVC rates it automatable
What to do
Check whether your setup matches what the bug needs.
WordPress MCP Server for WordPress plugin version 2.0.1 or earlierUpgrade to a fixed version: 2.0.2.
Timeline
- CVE published
- First seen by cve.now
- CISA SSVC assessment
Exploitation: none · Automatable: no · Technical impact: total
- Record last updated
Affected versions
- ai-workflow-automation-ai-agent-hub
through 2.0.1
Evidence 1
- Link
Corrections
None so far.
Something wrong on this page? Report an error. Every fix is listed here.
Questions about CVE-2026-121576
Is CVE-2026-121576 being exploited?
It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. No public exploit code is tracked.Source: cve.now feed data
What does this mean?
A low-privilege user can gain admin rights on the WordPress site and take full control of it. The flaw is a privilege escalation bug in the MCP Server for WordPress plugin.Source: patchstack.com, cve.org
Which versions are affected by CVE-2026-121576?
ai-workflow-automation-ai-agent-hub: through 2.0.1.Source: cve.now feed data
Am I affected, and how do I check?
The plugin versions from 0 up to and including 2.0.1 are in scope. The installed version can be checked on the Plugins screen of the WordPress admin, or in the plugin's header details.Source: patchstack.com, cve.org
How do I fix CVE-2026-121576?
Update the MCP Server for WordPress plugin to version 2.0.2 or later, which the advisory names as the fixed release.Source: patchstack.com, cve.org