CVE-2024-43265

Analytify <= 5.3.1 - Cross-Site Request Forgery to Opt-out

2024-08-12 00:00
Dhabaleshwar Das

Strategic Overview

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

At a glance

CVE-2024-43265 is a medium-severity Missing Authorization vulnerability in the Analytify WordPress plugin, affecting versions <= 5.3.1. It carries a CVSS score of 4.3 (reachable over the network; low attack complexity). The issue is fixed in version 5.4.0; sites on affected versions should update now. Disclosed August 2024, reported by Dhabaleshwar Das.

Vulnerability Overview

The Analytify – Google Analytics Dashboard For WordPress (GA4 analytics made easy) plugin for WordPress is vulnerable to Cross-Site Request Forgery in all versions up to, and including, 5.3.1. This is due to missing or incorrect nonce validation on the optout_yes() function. This makes it possible for unauthenticated attackers to opt out of tracking via a forged request granted they can trick a site administrator into performing an action such as clicking on a link.

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.3.1 carries this weakness at optout_yes(), and reaching it 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 5.4.0: builds <= 5.3.1 are affected, anything from 5.4.0 onward is not.

Remediation

Update to version 5.4.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 5.4.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-2024-43265https://www.wordfence.com/threat-intel/vulnerabilities/id/0e407409-989d-48f8-8135-6071015a6064https://nvd.nist.gov/vuln/detail/CVE-2024-43265

Related records

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