Analytify – Google Analytics Dashboard For WordPress (GA4 analytics made easy) <= 5.2.3 - Cross-Site Request Forgery
Strategic Overview
- Status
- Patched in 5.2.4
- Affected Version
<= 5.2.3- CVSS
- 4.3Medium
- Weakness type
- CWE-352 · Cross-Site Request Forgery (CSRF)
- CVE
CVE-2024-35689
At a glance
CVE-2024-35689 is a medium-severity Cross-Site Request Forgery (CSRF) vulnerability in the Analytify WordPress plugin, affecting versions <= 5.2.3. It carries a CVSS score of 4.3 (reachable over the network; low attack complexity). Exploitation requires no authentication. The issue is fixed in version 5.2.4; sites on affected versions should update now. Disclosed June 2024, reported by Majed Refaea.
Vulnerability Overview
The Analytify – Google Analytics Dashboard For WordPress (GA4 analytics made easy) plugin for WordPress is vulnerable to Cross-Site Request Forgery in all versions up to, and including, 5.2.3. This is due to missing or incorrect nonce validation on the wpa_check_authentication() function. This makes it possible for unauthenticated attackers to update the Google Analytics tracking code via a forged request granted they can trick a site administrator into performing an action such as clicking on a link.
Technical Analysis
The vector marks this flaw as remotely reachable over the network, with low attack complexity — no special timing or configuration is needed, and no privileges on the target site.
CWE-352: Cross-Site Request Forgery (CSRF)
Analytify <= 5.2.3 carries this weakness at wpa_check_authentication(), and reaching it takes a caller who can reach the endpoint. Cross-site request forgery abuses the fact that browsers attach a victim's cookies to any request, so a state-changing action that only checks who you are, not whether you meant to act, can be triggered from another site.
An attacker who gets a logged-in user to load a crafted page can perform that action as them, with the impact scaling to whatever the victim's role is allowed to do. For Analytify the fix is 5.2.4: builds <= 5.2.3 are affected, anything from 5.2.4 onward is not.
Remediation
Update to version 5.2.4, or a newer patched version
How does WordSec protect against this?
The attempt arrives as an ordinary request to Analytify: WordSec's web application firewall inspects request payloads before WordPress loads them. None of that substitutes for the fix: Analytify 5.2.4 closes this, and updating the plugin is the step that ends it.
- Firewall
- Alerts
External References
Related records
Same weakness class
Other vulnerabilities in Analytify – Google Analytics Dashboard For WordPress (GA4 analytics tracking)
- 6.5Analytify Authorization Bypass
- 6.1Analytify <= 4.2.0 Reflected Cross-Site Scripting
- 5.4CVE-2024-1809: Analytify Missing Authorization
CVE-2024-1809 - 5.3CVE-2024-1584: Analytify Unauthenticated Google Analytics Tracking ID
CVE-2024-1584 - 4.3CVE-2025-30897: Analytify Authenticated (Subscriber+) Minor Settings
CVE-2025-30897 - 4.3CVE-2025-26773: Analytify <= 5.5.0 Missing Authorization
CVE-2025-26773 - 4.3CVE-2024-53814: Analytify <= 5.4.3 Missing Authorization
CVE-2024-53814 - 4.3CVE-2024-43265: Analytify <= 5.3.1 CSRF to Opt-out
CVE-2024-43265
Vulnerability data © Defiant, Inc., provided under the Wordfence Intelligence T&C