CVE-2026-15015
MountDev AI MCP Connector for WordPress <= 1.6.1 - Unauthenticated Privilege Escalation via OAuth Authorization Endpoint
No known exploitation. EPSS puts it in the 85th percentile. No fix published yet.
What to do
No fixed build or workaround is published yet. Limit exposure and watch for a patch.
- cascadiawebservices MountDev AI MCP Connector for WordPressAffected: ≤ 1.6.1Upgrade to: after 1.6.1Stated by: CVE record
Versions as the sources state them. Full version matrix after sign-in
Steps
Written by AI from the record- Check whether MountDev AI MCP Connector for WordPress is installed and its version is 1.6.1 or older.
- If it is, immediately disable/remove the plugin from your WordPress site until a fix is available.
- Contact your plugin vendor/host to request the patched version for MountDev AI MCP Connector for WordPress and to confirm whether any interim mitigation exists.
- Review WordPress admin users, recent changes, and any OAuth/client activity in your WordPress configuration/logs since installation/last update.
What it is
From the CVE record
The MountDev AI MCP Connector for WordPress plugin for WordPress is vulnerable to authorization bypass in all versions up to, and including, 1.6.1. This is due to the plugin not properly verifying that a user is authorized to perform an action. This makes it possible for unauthenticated attackers to obtain an administrator-bound OAuth Bearer token via a self-registered client, granting full administrator-equivalent access to the plugin's MCP tool surface and all exposed WordPress content, users, and options. This is exploitable by combining the publicly accessible Dynamic Client Registration endpoint, which allows unauthenticated callers to register arbitrary OAuth clients with an attacker-controlled redirect_uri, with the unprotected authorization endpoint to complete the full OAuth flow without any administrator interaction.
In plain language
Written by AI from the recordIf you run MountDev AI MCP Connector for WordPress version 1.6.1 or older, attackers can get administrator-level access without logging in, letting them take over the plugin and view/change your WordPress content—this is a serious risk that you should act on now.
CVE-2026-15015 is an authorization-check bypass in MountDev AI MCP Connector for WordPress (≤ 1.6.1) that allows unauthenticated attackers to register an arbitrary OAuth client and obtain an administrator-equivalent OAuth Bearer token via the public Dynamic Client Registration and authorization endpoints, resulting in full plugin control and access to WordPress data and settings.
If you're affected
- Full WordPress takeover
- Site content and user changes
- Exposure of WordPress data
- Operational disruption
Exploitation
Where each signal puts this CVE on the scale from published to confirmed exploited.
- CISA KEV
Not in the catalog. CISA has not confirmed exploitation.
- Public exploits
No public exploit or proof of concept found in the sources we track.
- EPSS
2.6% chance of exploitation activity in the next 30 days, which ranks it in the 85th percentile of scored CVEs.
Exploit Prediction Scoring System, FIRST.org. A probability, not a confirmation.
Lifecycle
6 events over 90 days, from the signal feeds we watch.
- Nuclei check added
- Publishedweakness classified, att&ck mapped, record updated, record updated
Affected products
Technical detail
CVSS 3.1 vector
Open in the CVSS calculatorCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
Scored 9.8 by NVD.
How it is reached
- Attack Vector NetworkExploitable remotely over the network without any special conditions
- Attack Complexity LowNo special conditions — the attack can be reliably reproduced
- Privileges Required NoneNo authentication required — anyone can exploit this
- User Interaction NoneNo user interaction needed — fully automated exploitation
Scope
- Scope UnchangedImpact is limited to the vulnerable component itself
Impact if exploited
- Confidentiality HighTotal information disclosure — all data in the component is compromised
- Integrity HighTotal loss of integrity — attacker can modify any data in the component
- Availability HighTotal denial of service — the component is completely unavailable
Weaknesses
ATT&CK techniques
Mapped from the weaknesses above (CWE to ATT&CK), not observed in attacks.
Sources
References in the record
- wordfence.com/threat-intel/vulnerabilities/id/ce8ec66f-5efc-4354-8871-8e35ab4e51fc?source=cve
- plugins.trac.wordpress.org/browser/mountdev-ai-mcp-connector/tags/1.6.0/includes/class-oauth-controller.php
- plugins.trac.wordpress.org/browser/mountdev-ai-mcp-connector/tags/1.6.0/includes/class-oauth-controller.php
And 3 more references. See all after sign-in
Watch the software you run.
My Stack ranks new CVEs for your products by real-world exploitation, so the next serious one reaches you without reading every advisory.
We'll flag the next CVE, public exploit or patch for Cascadiawebservices, not every advisory.
A free account adds
- The full version matrix and every affected product
- Exploit links, proofs of concept and Metasploit modules
- Email alerts for the products you watch
- The same data over REST API, MCP and CLI