dbcve.org
Analytify Google Analytics DashboardWordPress extension · Analytify

CVE-2024-35689

HIGH · 8.8 CVSS v3.1 Published 2024-06-08
Fix available
A fix is available. Upgrade to 5.2.4 or later.
See remediation →
95/100
Remediation priority · Urgent
Remotely reachable No privileges

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
Cross-Site Request Forgery (CSRF) vulnerability in Analytify.This issue affects Analytify: from n/a through 5.2.3.

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

Cross-Site Request Forgery (CSRF) vulnerability in the Analytify WordPress plugin affecting versions up to 5.2.3. The vulnerability allows remote attackers to trick authenticated administrators into performing unwanted actions via maliciously crafted requests.

MitigationImplement WordPress nonces (anti-CSRF tokens) on all state-changing admin actions and verify the nonce validation is enforced before processing any form submissions or AJAX requests.

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.2.4

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
Required
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/UI:R/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 installation
    In WordPress admin, go to Plugins > Installed Plugins and look for 'Analytify Analytify Google Analytics Dashboard'. Note the version number displayed below the plugin name.
    Affected if Plugin is installed with version 5.2.3 or earlier (< 5.2.4)
  2. Check WordPress plugins directory
    Via FTP or file manager, navigate to /wp-content/plugins/ and check for the analytify folder. Open the main plugin file (usually analytify.php) and locate the 'Version' header comment.
    Affected if Version header shows a number less than 5.2.4
  3. Inspect admin action handlers for nonce validation
    Examine PHP files in the analytify plugin folder (particularly in admin/ subdirectories) for WordPress nonce verification functions such as wp_verify_nonce(), check_admin_referer(), or check_ajax_referer() in functions handling form submissions or AJAX requests.
    Affected if Admin action handlers lack nonce verification calls before processing state-changing requests
  4. Verify nonce field presence in admin forms
    View page source of Analytify plugin admin pages (e.g., Analytics > Dashboard, Analytics > Settings) and search for hidden nonce fields (input elements with name containing '_nonce' or 'wpnonce') in forms that perform settings changes or data submissions.
    Affected if Forms submitting to admin-post.php or AJAX endpoints lack hidden nonce input fields

A user is affected if the Analytify plugin version is below 5.2.4 AND admin forms/AJAX handlers in the plugin do not implement WordPress nonce verification before processing requests.

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.2.4 or later
Fixed in 5.2.4
Interim mitigation

Implement WordPress nonces (anti-CSRF tokens) on all state-changing admin actions and verify the nonce validation is enforced before processing any form submissions or AJAX requests.

Recommended fix High confidence

Analytify Google Analytics Dashboard version 5.2.4

  1. Backup your WordPress site before performing any updates
  2. Navigate to WordPress admin dashboard > Plugins > Installed Plugins
  3. Find Analytify (Google Analytics Dashboard) in the plugin list
  4. Click 'Update Now' if an update is available, or manually upload version 5.2.4 of the Analytify plugin
  5. Verify the plugin version is now 5.2.4 in the Plugins list
  6. Test that the Analytify functionality works correctly (viewing Analytics data, saving settings)

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
  • Testing2.0 h
  • Review / QA1.0 h
9.0 hours of engineering $1,600
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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