dbcve.org
Improper Privilege ManagementWeakness · CWE-269

CVE-2026-9810

CRITICAL · 9.8 CVSS v3.1 Published 2026-07-17
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 5 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 AI Copilot WordPress plugin before 1.5.4 does not bind OAuth access tokens to a WordPress user, and accepts any valid token as an administrator session, allowing unauthenticated attackers who complete the public OAuth flow to execute privileged MCP tools as an administrator, including arbitrary user creation and role escalation.

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 AI Copilot WordPress plugin before 1.5.4 fails to bind OAuth access tokens to WordPress user sessions, instead accepting any valid OAuth token as a valid administrator session. This allows unauthenticated attackers who complete the public OAuth flow to execute privileged MCP tools with full administrator privileges, enabling arbitrary user creation and role escalation.

MitigationUpgrade to AI Copilot plugin version 1.5.4 or later which properly binds OAuth tokens to WordPress user sessions. Until patched, monitor for unauthorized admin account creation and review OAuth configuration.

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. Check AI Copilot plugin version
    Navigate to WordPress admin > Plugins > Installed Plugins > locate 'AI Copilot' and view the Version number. Alternatively, inspect the plugin main file header for the 'Version' tag.
    Affected if The installed version is earlier than 1.5.4 (e.g., 1.5.3, 1.5.2, 1.0.0, etc.)
  2. Verify OAuth authentication is configured
    Check the plugin settings page for OAuth-related configuration. Look for fields indicating OAuth client ID, client secret, or connected account status. Inspect network requests or plugin database options for 'oauth', 'token', or 'copilot' related keys.
    Affected if OAuth authentication is enabled or configured, allowing the public OAuth flow to be initiated.
  3. Confirm MCP tools endpoint is accessible
    Probe the plugin endpoint for MCP (Model Context Protocol) tool execution. Common paths include /wp-json/ai-copilot/mcp, /?rest_route=/ai-copilot/mcp, or similar. Use a tool like curl to send a request and observe if MCP tools respond.
    Affected if The MCP endpoint returns a valid response or accepts requests, indicating the privileged tools are exposed.
  4. Inspect token validation behavior
    Use a valid OAuth token from a legitimate admin session, then attempt to use that same token in a different browser session or from another IP address. Observe whether the plugin accepts the token without verifying it corresponds to the current WordPress user session.
    Affected if The plugin accepts an OAuth token from any session or IP without validating that the token is bound to the specific authenticated WordPress user session making the request.

A user is affected if the AI Copilot plugin version is below 1.5.4 AND OAuth is configured, allowing the MCP endpoint to execute privileged actions with any valid OAuth token regardless of the requesting user session.

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.

dbcve · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Upgrade to AI Copilot plugin version 1.5.4 or later which properly binds OAuth tokens to WordPress user sessions. Until patched, monitor for unauthorized admin account creation and review OAuth configuration.

Recommended fix Moderate confidence

1.5.4

  1. 1. Log in to the WordPress admin dashboard
  2. 2. Navigate to Plugins > Installed Plugins
  3. 3. Locate the AI Copilot plugin in the plugin list
  4. 4. If an update is available, click 'Update Now' to upgrade to version 1.5.4
  5. 5. Alternatively, navigate to Plugins > Add New > Upload Plugin and upload version 1.5.4 of the AI Copilot plugin
  6. 6. After updating, verify the plugin version is 1.5.4 or higher under Plugins > Installed Plugins
  7. 7. Test that the OAuth functionality works correctly after the update

Generated from the published advisory — verify against the referenced sources before acting.

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation3.0 h
  • Testing4.0 h
  • Review / QA2.0 h
11.0 hours of engineering $1,900
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-9810 — 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-9810 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