dbcve.org
Missing AuthorizationWeakness · CWE-862

CVE-2026-15015

CRITICAL · 9.8 CVSS v3.1 Published 2026-07-23
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable No privileges Zero-click 4 weeks old

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
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.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

The MountDev AI MCP Connector for WordPress plugin versions up to 1.6.1 has a critical authorization bypass vulnerability. The Dynamic Client Registration endpoint is publicly accessible without authentication, allowing attackers to register OAuth clients with attacker-controlled redirect_uris. Combined with the unprotected authorization endpoint, this enables unauthenticated attackers to complete the full OAuth flow and obtain administrator-bound Bearer tokens, granting full admin-equivalent access to the plugin's MCP tools and all WordPress content, users, and options.

MitigationRestrict the Dynamic Client Registration endpoint to authenticated administrators only and add proper authorization checks to the authorization endpoint. Invalidate all existing OAuth tokens and client registrations, then monitor for unauthorized access. Update to the latest patched version when available.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

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

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Confirm plugin installation
    Check if the MountDev AI MCP Connector plugin exists in WordPress. Inspect the plugin directory at wp-content/plugins/ for a folder named 'mountdev-ai-mcp-connector' or query the WordPress database: SELECT option_value FROM wp_options WHERE option_name = 'active_plugins'
    Affected if The plugin is installed and active in WordPress
  2. Identify installed version
    Read the plugin header from the main PHP file (typically mountdev-ai-mcp-connector.php) in the plugin folder to find the Version field, or query: SELECT meta_value FROM wp_postmeta WHERE meta_key = 'plugin' AND post_id IN (SELECT ID FROM wp_posts WHERE post_title LIKE '%MountDev%')
    Affected if The version is unknown, unpatched, or falls within any unfixed range
  3. Test Dynamic Client Registration endpoint exposure
    Send an unauthenticated HTTP POST request to the plugin's OAuth registration endpoint (common paths: /?rest_route=/mcp-oauth/v1/register, /wp-json/mcp-oauth/v1/register, or /?oauth=register). Include a JSON body with a redirect_uri parameter pointing to an attacker-controlled domain, for example: {"redirect_uri":"https://attacker.example.com/callback"}
    Affected if The endpoint returns a successful response with client_id without requiring authentication
  4. Verify authorization endpoint authorization
    Send an unauthenticated HTTP GET request to the authorization endpoint (common paths: /?rest_route=/mcp-oauth/v1/authorize or /?oauth=authorize) with a client_id obtained from client registration and a redirect_uri parameter
    Affected if The endpoint issues an authorization code or token without verifying that the requester is an authenticated administrator
  5. Detect unauthorized OAuth clients
    Query the database for OAuth client records that were created unexpectedly. Check tables named similar to 'mcp_oauth_clients' or 'wp_mcp_oauth_clients', or inspect any plugin-specific options in wp_options where client_id values may be stored
    Affected if OAuth clients exist with redirect_uri values pointing to domains you do not recognize or did not create

If the MountDev AI MCP Connector plugin is installed and its OAuth endpoints (Dynamic Client Registration and/or Authorization) are accessible without authentication, the environment is vulnerable to CVE-2026-15015.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

From vendor data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Restrict the Dynamic Client Registration endpoint to authenticated administrators only and add proper authorization checks to the authorization endpoint. Invalidate all existing OAuth tokens and client registrations, then monitor for unauthorized access. Update to the latest patched version when available.

Have this fixed Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing4.0 h
  • Review / QA3.0 h
19.0 hours of engineering $3,380
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,408.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-15015 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-15015 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data