CVE-2022-45830

Analytify <= 4.2.3 - Missing Authorization & Cross-Site Request Forgery

2023-01-03 00:00
Tien Nguyen Ahn

Strategic Overview

Status
Patched in 4.3.0
Affected Plugin
Analytify – Google Analytics Dashboard For WordPress (GA4 analytics tracking)
Affected Version
<= 4.2.3
CVSS
4.3Medium
Weakness type
CWE-352 · Cross-Site Request Forgery (CSRF)
CVE
CVE-2022-45830
View all Analytify – Google Analytics Dashboard For WordPress (GA4 analytics tracking) vulnerabilities

At a glance

CVE-2022-45830 is a medium-severity Cross-Site Request Forgery (CSRF) vulnerability in the Analytify WordPress plugin, affecting versions <= 4.2.3. It carries a CVSS score of 4.3 (reachable over the network; low attack complexity). Exploitation requires no authentication. The issue is fixed in version 4.3.0; sites on affected versions should update now. Disclosed January 2023, reported by Tien Nguyen Ahn.

Vulnerability Overview

The Analytify plugin for WordPress is vulnerable to authorization bypass & Cross-Site Request Forgery in versions up to, and including, 4.2.3. This is due to missing nonce validation and a lack of capability checking on the logout() function. This makes it possible for unauthenticated attackers to invoke this function and log out an associated Google Analytics account either themself or via 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 privileges on the target site.

CWE-352: Cross-Site Request Forgery (CSRF)

Analytify <= 4.2.3 carries this weakness at logout(), and reaching it takes a caller who can reach the endpoint. Cross-site request forgery abuses the fact that browsers attach a victim's cookies to any request, so a state-changing action that only checks who you are, not whether you meant to act, can be triggered from another site.

An attacker who gets a logged-in user to load a crafted page can perform that action as them, with the impact scaling to whatever the victim's role is allowed to do. For Analytify the fix is 4.3.0: builds <= 4.2.3 are affected, anything from 4.3.0 onward is not.

Remediation

Update to version 4.3.0, or a newer patched version

How does WordSec protect against this?

The attempt arrives as an ordinary request to Analytify: WordSec's web application firewall inspects request payloads before WordPress loads them. None of that substitutes for the fix: Analytify 4.3.0 closes this, and updating the plugin is the step that ends it.

  • Firewall
  • Alerts

External References

https://www.cve.org/CVERecord?id=CVE-2022-45830https://www.wordfence.com/threat-intel/vulnerabilities/id/a462789a-d311-47d7-9f54-190eaf5da03fhttps://nvd.nist.gov/vuln/detail/CVE-2022-45830

Related records

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