Analytify – Google Analytics Dashboard For WordPress <= 4.2.2 - Authorization Bypass

2022-08-22 00:00
Anonymous

Strategic Overview

Status
Patched in 4.2.3
Affected Version
<= 4.2.2
CVSS
6.5Medium
Weakness type
CWE-862 · Missing Authorization
CVE
CVE pending
View all Analytify – Google Analytics Dashboard For WordPress (GA4 analytics tracking) vulnerabilities

At a glance

This record tracks a medium-severity Missing Authorization vulnerability in the Analytify WordPress plugin, affecting versions <= 4.2.2. It carries a CVSS score of 6.5 (reachable over the network; low attack complexity; high integrity impact). The issue is fixed in version 4.2.3; sites on affected versions should update now. Disclosed August 2022.

Vulnerability Overview

The Analytify plugin for WordPress is vulnerable to authorization bypass due to a missing capability and nonce checks on the analytify_delete_cache function in versions up to, and including, 4.2.2 . This makes it possible for authenticated attackers, with subscriber-level permissions and above, to delete the cache of the plugin and also allows unauthenticated attackers to delete the plugin cache via forged request, granted they can trick a subscriber or higher into clicking on a link. Version 4.2.3 adds a nonce check to the function, which addressed the Cross-Site Request Forgery Vulnerability and makes exploitation impractical for lower-level accounts.

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. A successful exploit has high impact on integrity.

CWE-862: Missing Authorization

Reaching this weakness in Analytify <= 4.2.2 takes a caller who can reach the endpoint. 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 4.2.3: builds <= 4.2.2 are affected, anything from 4.2.3 onward is not.

Remediation

Update to version 4.2.3, 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 4.2.3 closes this, and updating the plugin is the step that ends it.

  • Login Security
  • Alerts

External References

Related records

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