Analytify <= 5.2.1 - Missing Authorization to Unauthenticated Google Analytics Tracking ID Modification
Strategic Overview
- Status
- Patched in 5.2.4
- Affected Version
<= 5.2.3- CVSS
- 5.3Medium
- Weakness type
- CWE-284 · Improper Access Control
- CVE
CVE-2024-1584
At a glance
CVE-2024-1584 is a medium-severity Improper Access Control vulnerability in the Analytify WordPress plugin, affecting versions <= 5.2.3. It carries a CVSS score of 5.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 April 2024, reported by Francesco Carlucci.
Vulnerability Overview
The Analytify – Google Analytics Dashboard For WordPress (GA4 analytics made easy) plugin for WordPress is vulnerable to unauthorized modification of data due to a missing capability check on the 'wpa_check_authentication' function in all versions up to, and including, 5.2.1. This makes it possible for unauthenticated attackers to modify the site's Google Analytics tracking ID.
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, and no interaction from a victim user.
CWE-284: Improper Access Control
Analytify <= 5.2.3 carries this weakness at wpa_check_authentication, and reaching it takes no account at all. Improper access control means the code decides what a caller may do using something other than their actual permissions, so the decision can be wrong without any check appearing to be missing.
Whoever can shape the request decides the answer, so the protected action runs for callers the code never meant to allow. 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?
This one needs no account at all, which puts it outside what login hardening can reach; WordSec's login security narrows the account-level paths around it, and the firewall is what inspects the request itself. None of that substitutes for the fix: Analytify 5.2.4 closes this, and updating the plugin is the step that ends it.
- Login Security
- Alerts
External References
Related records
Other vulnerabilities in Analytify – Google Analytics Dashboard For WordPress (GA4 analytics tracking)
- 8.8CVE-2022-38137: Analytify CSRF
CVE-2022-38137 - 6.5Analytify Authorization Bypass
- 6.1Analytify <= 4.2.0 Reflected Cross-Site Scripting
- 5.4CVE-2024-1809: Analytify Missing Authorization
CVE-2024-1809 - 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