dbcve.org
Missing AuthorizationWeakness · CWE-862

CVE-2026-5371

HIGH · 7.1 CVSS v3.1 Published 2026-05-12
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
77/100
Remediation priority · High
Remotely reachable Zero-click

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 MonsterInsights – Google Analytics Dashboard for WordPress (Website Stats Made Easy) plugin for WordPress is vulnerable to unauthorized access and modification of data due to a missing capability checks on the get_ads_access_token() and reset_experience() functions in all versions up to, and including, 10.1.2. This makes it possible for authenticated attackers, with Subscriber-level access and above, to retrieve live Google OAuth access tokens and reset Plugins's Google Ads integration.

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 MonsterInsights WordPress plugin lacks capability checks on the get_ads_access_token() and reset_experience() functions, allowing any authenticated user with Subscriber-level access or higher to retrieve live Google OAuth access tokens and reset the plugin's Google Ads integration. This is a broken access control vulnerability where sensitive functions are exposed to low-privilege users.

MitigationUpdate to version 10.1.3 or later which adds proper capability checks. Until then, consider disabling the plugin or restricting user registration to prevent unauthorized access.

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
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
Low
Availability
None

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

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. Verify MonsterInsights plugin is installed
    Navigate to Plugins > Installed Plugins in WordPress admin and look for 'MonsterInsights' in the list. Note whether it is installed and active.
    Affected if The MonsterInsights plugin is installed and active on the WordPress site.
  2. Check installed MonsterInsights version
    In the Plugins list, find MonsterInsights and note the version number displayed under the plugin name. Compare this to version 10.1.3.
    Affected if The installed version is lower than 10.1.3, meaning the capability checks are not present.
  3. Confirm user registration is enabled
    Go to Settings > General in WordPress admin and check if 'Membership' > 'Anyone can register' is ticked. If enabled, any visitor can create a Subscriber account.
    Affected if User registration is enabled, allowing creation of low-privilege subscriber accounts.
  4. Identify subscriber-level users
    Go to Users > All Users in WordPress admin. Review the list for any users with the 'Subscriber' role assigned.
    Affected if There are users with Subscriber role, who can exploit the vulnerable functions.
  5. Check plugin API endpoints exposure
    Inspect network traffic or access the AJAX endpoint for get_ads_access_token (typically /wp-admin/admin-ajax.php?action=minsights_get_ads_access_token) while logged in as a Subscriber user to confirm the function responds without permission error.
    Affected if The endpoint returns a valid response or token rather than a capability error, confirming the vulnerability is exploitable.

You are affected if MonsterInsights plugin is installed with a version lower than 10.1.3, user registration is open or low-privilege subscriber accounts exist, and the API endpoints respond without proper capability validation.

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

Update to version 10.1.3 or later which adds proper capability checks. Until then, consider disabling the plugin or restricting user registration to prevent unauthorized access.

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation2.0 h
  • Testing2.0 h
  • Review / QA1.0 h
7.0 hours of engineering $1,240
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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