CVE-2025-30897

Analytify <= 5.5.1 - Missing Authorization to Authenticated (Subscriber+) Minor Settings Update

2025-03-27 00:00
Trương Hữu Phúc (truonghuuphuc)

Strategic Overview

Status
Patched in 6.0.0
Affected Plugin
Analytify – Google Analytics Dashboard For WordPress (GA4 analytics tracking)
Affected Version
<= 5.5.1
CVSS
4.3Medium
Weakness type
CWE-862 · Missing Authorization
CVE
CVE-2025-30897
View all Analytify – Google Analytics Dashboard For WordPress (GA4 analytics tracking) vulnerabilities

At a glance

CVE-2025-30897 is a medium-severity Missing Authorization vulnerability in the Analytify WordPress plugin, affecting versions <= 5.5.1. It carries a CVSS score of 4.3 (reachable over the network; low attack complexity). Exploitation requires an authenticated account at Subscriber level or above. The issue is fixed in version 6.0.0; sites on affected versions should update now. Disclosed March 2025, reported by Trương Hữu Phúc (truonghuuphuc).

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 rated() function in all versions up to, and including, 5.5.1. This makes it possible for authenticated attackers, with Subscriber-level access and above, to set the rated option to true.

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 interaction from a victim user.

CWE-862: Missing Authorization

Analytify <= 5.5.1 carries this weakness at rated(), and reaching it takes an account at Subscriber level or above. A missing authorization check means a function is reachable by anyone who can reach the endpoint, because the code never asks whether the caller is allowed to perform the action.

Any user who can reach the endpoint gets to run an action reserved for higher-privileged roles, from reading protected data to changing settings or content. For Analytify the fix is 6.0.0: builds <= 5.5.1 are affected, anything from 6.0.0 onward is not.

Remediation

Update to version 6.0.0, or a newer patched version

How does WordSec protect against this?

Because it turns on account access, WordSec's login security is the relevant layer: role-based two-factor, captcha and brute-force limits raise the cost of getting the account this needs. None of that substitutes for the fix: Analytify 6.0.0 closes this, and updating the plugin is the step that ends it.

  • Login Security
  • Alerts

External References

https://www.cve.org/CVERecord?id=CVE-2025-30897https://www.wordfence.com/threat-intel/vulnerabilities/id/feb13137-4708-43da-9a5a-b7af8356942dhttps://nvd.nist.gov/vuln/detail/CVE-2025-30897

Related records

Vulnerability data © Defiant, Inc., provided under the Wordfence Intelligence T&C