Skip to main content
Menu
CVEs

CVE

AtlasAiDev MCP Server for WordPress privilege escalation via incorrect role assignment

CVE-2026-125771EUVD-2026-126090GHSA-W68M-3RVM-5XXQ

CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:H

7.2HighCNA
Exploited
No known exploitation
Fix
Fixed in 2.0.4
Who is exposed
Specific setups only

Do first: Check whether your setup matches what the bug needs. MCP Server for WordPress plugin version 2.0.3 or earlier

Published
Last modified
Reference
Last checked
0.26% · 17th percentile
16/100 · provisional
Specific setups only
None on Exploit-DB, Metasploit or GitHub
  • Exploitation: none
  • Automatable: no
  • Technical impact: total

Summary

The MCP Server for WordPress plugin from AtlasAiDev has an incorrect privilege assignment flaw that allows privilege escalation. An attacker must already be logged in with high privileges, but can reach the flaw remotely over the network without any user interaction.

Written by anthropic/claude-haiku-5.5 from the sources below. Verify against them.

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.3.

Who should check

Sites running the MCP Server for WordPress plugin (ai-workflow-automation-ai-agent-hub) version 2.0.3 or earlier, from AtlasAiDev.

“WordPress MCP Server for WordPress Plugin <= 2.0.3 is vulnerable to a high priority Privilege Escalation”

patchstack.com

cve.now Index

16Pcve.now Index 16 of 100 · methodology v3 · provisional
  • Exploitation0/40No signal
  • Exposure8/25Specific setups only, reachable over the network
  • Reach?/20Unknown. No tracked technology or package matched
  • Severity8.2/10CVSS 7.2, total technical impact per CISA
  • No patch0/5No signal

What would change the score

  • Would score about 66 if added to CISA KEV
  • Would score about 61 if CISA's SSVC rates exploitation active
  • Would score about 23 if CISA's SSVC rates it automatable

What to do

  • Check whether your setup matches what the bug needs.

    MCP Server for WordPress plugin version 2.0.3 or earlier
  • Upgrade to a fixed version: 2.0.4.

Check your systems with an agent

Paste this into a coding or ops agent. It checks your systems read-only and reports a table per asset.

Check whether my systems are affected by CVE-2026-125771 (WordPress MCP Server for WordPress plugin <= 2.0.3 - Privilege Escalation vulnerability), using the cve.now data below.

Rules: work read-only. Do not run exploit code, proof-of-concept scripts or scanners that send attack payloads, and do not change any configuration, package, image or deployment. Report findings only.

What cve.now has for CVE-2026-125771 (entry last updated 2026-11-16):
Affected:
- AtlasAiDev MCP Server for WordPress: through 2.0.3
Fixed versions: 2.0.4.
Conditions (all must be true for the bug to be hit):
- MCP Server for WordPress plugin version 2.0.3 or earlier (source: https://patchstack.com/database/wordpress/plugin/ai-workflow-automation-ai-agent-hub/vulnerability/wordpress-mcp-server-for-wordpress-plugin-2-0-3-privilege-escalation-vulnerability?_s_id=cve)
Setup: unknown whether the bug needs a non-default feature or setting. Check the advisory.
Attacker needs: network access, high-privilege login, no user action.
CISA KEV: CVE-2026-125771 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-125771 only. If you also check another CVE, look up its own KEV status; never assume it from this one.

How to check:
- Installed software: check what is actually running, not what a repo declares. Read the version from each host, container image and Kubernetes node (the binary's version output, the OS package database, image layers), and check whether the conditions above hold there. Distribution packages may carry a backported fix under an older version number; confirm against the distribution's own advisory.

Verify against the linked advisories before concluding, and cite the date you read each one:
- https://patchstack.com/database/wordpress/plugin/ai-workflow-automation-ai-agent-hub/vulnerability/wordpress-mcp-server-for-wordpress-plugin-2-0-3-privilege-escalation-vulnerability?_s_id=cve
Do not conclude an asset is unaffected unless you checked it and the evidence covers both its version and the conditions above. If you could not check something, mark it unknown and say what is missing.

Report a table with one row per asset and these columns: Asset | Version or build | Status (affected, fixed, not applicable, unknown) | Compensating controls | Exposure (internet-facing, internal, none) | Evidence | Next action.

Entry: https://cve.now/CVE-2026-125771
For follow-up questions, use the cve.now MCP server at https://mcp.cve.now/mcp (no authentication), for example execute with name cve.get and arguments {"id": "CVE-2026-125771"}.

Timeline

  1. CVE published
  2. First seen by cve.now1 day
  3. CISA SSVC assessment

    Exploitation: none · Automatable: no · Technical impact: total

  4. Record last updated

Affected versions

  • ai-workflow-automation-ai-agent-hub

    through 2.0.3

Evidence 3

CVE record · 2

Establishes: The identifier and description.

  1. Record
  2. Record

Other links · 1

  1. Link

Corrections

None so far.

Something wrong on this page? Report an error. Every fix is listed here.

Questions about CVE-2026-125771

Is CVE-2026-125771 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 become an admin and gain full control of the WordPress site through this plugin's privilege escalation flaw.Source: patchstack.com

Which versions are affected by CVE-2026-125771?

ai-workflow-automation-ai-agent-hub: through 2.0.3.Source: cve.now feed data

Am I affected, and how do I check?

The MCP Server for WordPress plugin by AtlasAiDev, version 2.0.3 and earlier, is affected. To check a site, look at the plugin version shown on the Plugins screen in the WordPress admin.Source: patchstack.com

How do I fix CVE-2026-125771?

Update the MCP Server for WordPress plugin to version 2.0.4 or later, which resolves the vulnerability.Source: patchstack.com