dbcve.org
Authorization Bypass (IDOR)Weakness · CWE-639

CVE-2026-1992

HIGH · 8.8 CVSS v3.1 Published 2026-03-11
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
94/100
Remediation priority · Urgent
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 ExactMetrics – Google Analytics Dashboard for WordPress plugin is vulnerable to Insecure Direct Object Reference in versions 8.6.0 through 9.0.2. This is due to the `store_settings()` method in the `ExactMetrics_Onboarding` class accepting a user-supplied `triggered_by` parameter that is used instead of the current user's ID to check permissions. This makes it possible for authenticated attackers with the `exactmetrics_save_settings` capability to bypass the `install_plugins` capability check by specifying an administrator's user ID in the `triggered_by` parameter, allowing them to install arbitrary plugins and achieve Remote Code Execution. This vulnerability only affects sites on which administrator has given other user types the permission to view reports and can only be exploited by users of that type.

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 ExactMetrics WordPress plugin contains an IDOR vulnerability where the `store_settings()` method uses a user-supplied `triggered_by` parameter instead of the authenticated user's ID for permission checks. Attackers with `exactmetrics_save_settings` capability can specify an administrator's user ID to bypass the `install_plugins` capability check, enabling arbitrary plugin installation and RCE.

MitigationUpdate to ExactMetrics version 9.0.3 or later. Audit user roles to identify and remediate accounts granted `exactmetrics_save_settings` capability without explicit trust, and consider revoking this permission from non-administrator users until the patch is applied.

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
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:L/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 ExactMetrics plugin is installed
    Navigate to WordPress admin > Plugins and look for ExactMetrics, or check via WP-CLI: wp plugin list --name=exactmetrics
    Affected if ExactMetrics plugin is active on the site
  2. Identify installed ExactMetrics version
    Go to Plugins > Installed Plugins > ExactMetrics, or use WP-CLI: wp plugin get exactmetrics
    Affected if Version is lower than 9.0.3 (the fixed release)
  3. Audit users with exactmetrics_save_settings capability
    Query the database or use a user role editor to list all users with the exactmetrics_save_settings capability. In WP-CLI: wp user list --all --fields=ID,user_login,roles | then check role capabilities via database or role editor plugin
    Affected if Any user account (especially non-administrator) has the exactmetrics_save_settings capability granted
  4. Verify install_plugins capability is properly enforced
    Review the store_settings() method in the ExactMetrics plugin code to confirm it uses the authenticated user's ID rather than the triggered_by parameter for permission checks. Check file: includes/functions.php or similar where store_settings is defined
    Affected if The code uses user-supplied triggered_by parameter without validating against current_user->ID
  5. Check for unexpected plugin installations
    Review the wp_options table for option_name = 'active_plugins' or use wp plugin list to see all active plugins. Look for any plugins installed without your authorization
    Affected if Unexpected or unknown plugins appear in the active plugin list

A site is affected if ExactMetrics version is below 9.0.3 AND any user account (particularly non-administrators) possesses the exactmetrics_save_settings capability, enabling potential privilege escalation and arbitrary plugin installation.

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

Update to ExactMetrics version 9.0.3 or later. Audit user roles to identify and remediate accounts granted `exactmetrics_save_settings` capability without explicit trust, and consider revoking this permission from non-administrator users until the patch is applied.

Recommended fix Moderate confidence

Latest version of ExactMetrics plugin (version 9.0.3 or higher)

  1. Log in to the WordPress admin dashboard
  2. Navigate to Plugins > Installed Plugins
  3. Locate ExactMetrics – Google Analytics Dashboard for WordPress
  4. Check the current version number
  5. If the installed version is between 8.6.0 and 9.0.2 inclusive, update the plugin to the latest available version
  6. After updating, verify the new version is installed
  7. Review user roles and capabilities to ensure only trusted users have the 'exactmetrics_save_settings' capability
  8. Consider removing the 'view reports' permission from untrusted user types if not strictly necessary

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

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

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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