CVE-2022-4974

Freemius SDK <= 2.4.2 - Missing Authorization Checks

2022-03-04 00:00
Anonymous

Strategic Overview

Status
Patched in 2.1.1
Affected Plugin
WPLP Cookie Consent – Cookie Banner & Consent Management for GDPR, CCPA & Google Consent Mode
Affected Version
< 2.1.1
CVSS
6.3Medium
Weakness type
CWE-862 · Missing Authorization
CVE
CVE-2022-4974
View all WPLP Cookie Consent – Cookie Banner & Consent Management for GDPR, CCPA & Google Consent Mode vulnerabilities

At a glance

CVE-2022-4974 is a medium-severity Missing Authorization vulnerability in the WPLP Cookie Consent WordPress plugin, affecting versions < 2.1.1. It carries a CVSS score of 6.3 (reachable over the network; low attack complexity). The root cause is a missing authorization check on a reachable function. The issue is fixed in version 2.1.1; sites on affected versions should update now. Disclosed March 2022.

Vulnerability Overview

The Freemius SDK, as used by hundreds of WordPress plugin and theme developers, was vulnerable to Cross-Site Request Forgery and Information disclosure due to missing capability checks and nonce protection on the _get_debug_log, _get_db_option, and the _set_db_option functions in versions up to, and including 2.4.2. Any WordPress plugin or theme running a version of Freemius less than 2.4.3 is vulnerable.

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

Reaching this weakness in WPLP Cookie Consent < 2.1.1 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 WPLP Cookie Consent the fix is 2.1.1: builds < 2.1.1 are affected, anything from 2.1.1 onward is not.

Remediation

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

  • Login Security
  • Alerts

External References

https://www.cve.org/CVERecord?id=CVE-2022-4974https://www.wordfence.com/threat-intel/vulnerabilities/id/39fb0499-9ab4-4a2f-b0db-ece86bcf4d42https://nvd.nist.gov/vuln/detail/CVE-2022-4974

Related records

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