Analytify <= 5.2.1 - Missing Authorization to Unauthenticated Google Analytics Tracking ID Modification

published 2024-05-02 2 y ago modified 2026-06-17 4 mo ago also EUVD-2024-17328

cvss: 5.3; version 3.1, CNA
cisa kev: Not listed; not in CISA's catalog
epss: 0.4%; EPSS 0.4% chance of exploitation in 30 days, percentile 38%
public exploits: 0; none known

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.

Patch / fix

fixed in 1 links 1

analytify analytify_-_google_analytics_dashboard 5.2.4

plugins.trac.wordpress.org/changeset?sfp_email=&sfph_mail=&reponame=&old=3072410%40wp… patch

CISA SSVC

Exploitation: none
Automatable: yes
Technical impact: partial
Assessed: 2 y ago (2024-05-16)

Exploit prediction

0.43% chance of exploitation in the next 30 days, higher than 38% of all scored CVEs (FIRST EPSS, 2026-11-08).

CVSS scores

assigned by	version	score	vector
CNA	3.1	5.3	CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:N

Affected products

hiddenpearls Analytify – Google Analytics Dashboard For WordPress (GA4 analytics tracking)

Classification

Weakness

CWE-284 Improper Access Control
CWE-862 Missing Authorization

Technology feeds

WordPress rss critical rss

References

Sources

CVE List CVE-2024-1584
NVD CVE-2024-1584

Fencer Vulns keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.

CPEs and fixed versions use Anchore's correction of NVD's data: Added CPE configurations because not yet analyzed by NVD.

Summary