dbcve.org
Missing AuthorizationWeakness · CWE-862

CVE-2025-24750

MEDIUM · 5.4 CVSS v3.1 Published 2025-01-24
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
60/100
Remediation priority · Elevated
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
Missing Authorization vulnerability in Syed Balkhi ExactMetrics google-analytics-dashboard-for-wp allows Exploiting Incorrectly Configured Access Control Security Levels.This issue affects ExactMetrics: from n/a through <= 8.1.0.

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 · moderate confidence

Missing authorization vulnerability in ExactMetrics (google-analytics-dashboard-for-wp) plugin allows attackers to exploit incorrectly configured access control security levels. The plugin fails to properly validate user permissions before allowing access to certain functionality, potentially enabling authenticated users to perform unauthorized actions.

MitigationUpdate ExactMetrics to version 8.2.0 or later which contains the authorization fix. Review and audit user roles with administrative access to the plugin to ensure only trusted personnel have elevated permissions.

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
Low
Integrity
Low
Availability
None

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/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 ExactMetrics plugin version
    In WordPress admin, go to Plugins > Installed Plugins and locate ExactMetrics. The version number is displayed under the plugin name. Alternatively, check the main plugin file (e.g., /wp-content/plugins/google-analytics-dashboard-for-wp/includes/admin/pages.php or the main plugin header file) for the 'Version' header comment.
    Affected if The installed version is lower than 8.2.0 (e.g., 8.1.x, 8.0.x, or earlier)
  2. Confirm the plugin is active
    In WordPress admin, go to Plugins > Installed Plugins and verify that ExactMetrics (Google Analytics Dashboard for WP) shows as 'Active' rather than 'Inactive' or 'Must-Use'.
    Affected if The plugin is installed and active in the WordPress environment
  3. Identify user roles with ExactMetrics administrative access
    In WordPress admin, navigate to ExactMetrics Settings > General or the user role settings section. Review which WordPress user roles (Administrator, Editor, Author, Contributor, Subscriber, or custom roles) are granted access to ExactMetrics functionality. Check Users > All Users and examine role assignments if role settings are not visible in plugin menus.
    Affected if Non-administrator roles (such as Editor, Author, or Contributor) are granted elevated permissions or access to plugin settings that should be restricted to Administrators
  4. Test for authorization bypass (if safe to do so)
    Using a lower-privilege user account (e.g., Editor role), attempt to access ExactMetrics settings pages, tools, or export features directly via URL (e.g., /wp-admin/admin.php?page=exactmetrics_settings). Observe whether access is granted without proper permission validation.
    Affected if A user with lower privileges can access or modify plugin settings or data that should require Administrator-level authorization

You are affected if ExactMetrics version is below 8.2.0 and the plugin is active, particularly if non-Administrator users have elevated access to plugin functionality.

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 ExactMetrics to version 8.2.0 or later which contains the authorization fix. Review and audit user roles with administrative access to the plugin to ensure only trusted personnel have elevated permissions.

Recommended fix Moderate confidence

Latest available version of ExactMetrics (greater than 8.1.0)

  1. Log in to the WordPress admin dashboard
  2. Navigate to Plugins > Installed Plugins
  3. Locate ExactMetrics (Google Analytics Dashboard for WP)
  4. Check the current installed version to confirm it is <= 8.1.0
  5. Click 'Update Now' to update the plugin to the latest version, or manually download the latest version from the WordPress plugin repository and upload it
  6. After updating, verify the new version number in the plugins list
  7. Test that the Google Analytics integration continues to work correctly
Caveat Minor - review plugin changelog for any settings or feature changes

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

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

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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