dbcve.org
Analytify Google Analytics DashboardWordPress extension · Analytify

CVE-2023-41695

HIGH · 8.8 CVSS v3.1 Published 2024-12-13
Fix available
A fix is available. Upgrade to 5.1.1 or later.
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
Missing Authorization vulnerability in Adnan Analytify wp-analytify allows Exploiting Incorrectly Configured Access Control Security Levels.This issue affects Analytify: from n/a through <= 5.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 the Analytify WordPress plugin allows attackers to exploit incorrectly configured access control security levels. The vulnerability exists in versions up to and including 5.1.0, enabling unauthorized access to certain plugin functions or data that should require proper authentication or privileges.

MitigationUpdate Analytify plugin to the latest version which should include proper authorization checks. If no update is available, review the plugin's access control configuration and add appropriate capability checks or nonce verification to vulnerable functions.

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

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
Analytify Google Analytics DashboardWordPress extension
Affected:< 5.1.1

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. Verify Analytify plugin is installed and active
    Log into WordPress admin, go to Plugins > Installed Plugins, and look for 'Analytify' or check the plugins directory in wp-content/plugins for the analytify folder
    Affected if The Analytify plugin folder exists and the plugin is activated in WordPress
  2. Check installed Analytify version number
    In WordPress admin, go to Plugins > Installed Plugins, find Analytify, and view the version number displayed under the plugin name; alternatively, read the main plugin file (e.g., analytify.php) and look for the 'Version' header comment
    Affected if The version is 5.1.0 or lower (any version below 5.1.1)
  3. Identify exposed admin AJAX or REST API endpoints
    Inspect the plugin source code in wp-content/plugins/analytify, looking for add_action calls registering wp_ajax_ or wp_ajax_nopriv_ hooks, and REST API route registrations; use a browser or curl to probe these endpoints without authentication
    Affected if The plugin registers AJAX or REST endpoints accessible to unauthenticated or low-privilege users without proper capability checks
  4. Review plugin access control configuration
    Examine the plugin PHP files for missing current_user_can(), check_admin_referer(), or nonce verification before sensitive operations; grep for function calls that handle analytics data export or settings modification
    Affected if Functions that should require authentication (like viewing analytics data or modifying settings) lack authorization checks like current_user_can() or nonce validation

A user is affected if the Analytify plugin version is 5.1.0 or lower and the plugin is active, as the missing authorization vulnerability could allow unauthorized access to plugin functions.

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
Upgrade available Upgrade to 5.1.1 or later
Fixed in 5.1.1
Interim mitigation

Update Analytify plugin to the latest version which should include proper authorization checks. If no update is available, review the plugin's access control configuration and add appropriate capability checks or nonce verification to vulnerable functions.

Recommended fix Moderate confidence

Analytify version 5.1.1

  1. Backup your WordPress site and database before performing any updates
  2. Update the Analytify plugin through WordPress admin: Navigate to Plugins > Installed Plugins > Find Analytify > Click Update Now
  3. Alternatively, update via WordPress dashboard when an update notification appears
  4. After updating, verify the plugin version shows 5.1.1 in Plugins > Installed Plugins
  5. Test that the Google Analytics integration continues to work correctly
  6. Review user role permissions to ensure proper access controls are functioning

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

Fix this in Analytify Google Analytics Dashboard Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA2.0 h
11.0 hours of engineering $1,930
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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