Analytify – Google Analytics 4 Tracking and Reporting in WordPress
wp-analytify · plugin
Known security vulnerabilities for Analytify – Google Analytics 4 Tracking and Reporting in WordPress. Find out in seconds which version runs on your site with WP Lens.
11 known vulnerabilities
1 critical · 5 exploitable without logging in · latest Mar 27, 2025
Listed on wordpress.org · latest 9.1.2 · last updated Sep 25, 2026 · 20K+ installs
wordpress.org status checked on Oct 2, 2026
Vulnerabilities
- Critical 9.8
CVE-2022-45830unauthenticated≤ 4.2.3
WordPress Analytify - Google Analytics Dashboard plugin <= 4.2.3 - Privilege Escalation vulnerability
- High 8.8
CVE-2024-35689unauthenticated · needs a click≤ 5.2.3
WordPress Analytify plugin <= 5.2.3 - Cross Site Request Forgery (CSRF) vulnerability
- High 8.8
CVE-2022-38137unauthenticated · needs a click≤ 4.2.2
WordPress Analytify plugin <= 4.2.2 - Cross-Site Request Forgery (CSRF) vulnerability
- High 8.8
CVE-2025-26773login required≤ 5.5.0
WordPress Analytify plugin <= 5.5.0 - Broken Access Control vulnerability
- High 8.8
CVE-2023-41695login required≤ 5.1.0
WordPress Analytify plugin <= 5.1.0 - Broken Access Control vulnerability
- Medium 6.5
CVE-2024-53814login required≤ 5.4.3
WordPress Analytify plugin <= 5.4.3 - Broken Access Control vulnerability
- Medium 5.4
CVE-2024-1809subscriber+≤ 5.2.3
Analytify – Google Analytics Dashboard For WordPress (GA4 analytics made easy) <= 5.2.3 - Missing Authorization
- Medium 5.3
CVE-2024-1584unauthenticated≤ 5.2.3
Analytify <= 5.2.1 - Missing Authorization to Unauthenticated Google Analytics Tracking ID Modification
- Medium 4.3
CVE-2025-30897login required≤ 5.5.1
WordPress Analytify plugin <= 5.5.1 - Settings Change vulnerability
- Medium 4.3
CVE-2023-47841login required≤ 5.1.1
WordPress Analytify plugin <= 5.1.1 - Broken Access Control vulnerability
- Low 3.5
CVE-2024-43265unauthenticated · needs a click≤ 5.3.1
WordPress Analytify plugin <= 5.3.1 - CSRF Leading to Optout Vulnerability
The access label is read from the record's own text (e.g. “subscriber+”: subscriber and above). When the text names no role, CVSS decides between “login required” and “high privilege”; no role name is invented. “Needs a click”: the attack depends on a logged-in user following a link (CSRF, reflected XSS).