CVE-2022-3995

TeraWallet – For WooCommerce <= 1.4.3 - Insecure Direct Object Reference

2022-10-31 00:00
Marco Wotschka

Strategic Overview

Status
Patched in 1.4.4
Affected Plugin
Wallet for WooCommerce
Affected Version
<= 1.4.3
CVSS
4.3Medium
Weakness type
CWE-639 · Authorization Bypass Through User-Controlled Key
CVE
CVE-2022-3995
View all Wallet for WooCommerce vulnerabilities

At a glance

CVE-2022-3995 is a medium-severity Authorization Bypass Through User-Controlled Key vulnerability in the Wallet for WooCommerce WordPress plugin, affecting versions <= 1.4.3. It carries a CVSS score of 4.3 (reachable over the network; low attack complexity). The issue is fixed in version 1.4.4; sites on affected versions should update now. Disclosed October 2022, reported by Marco Wotschka.

Vulnerability Overview

The TeraWallet plugin for WordPress is vulnerable to Insecure Direct Object Reference in versions up to, and including, 1.4.3. This is due to insufficient validation of the user-controlled key on the lock_unlock_terawallet AJAX action. This makes it possible for authenticated attackers, with subscriber-level permissions and above, to lock/unlock other users wallets.

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-639: Authorization Bypass Through User-Controlled Key

Reaching this weakness in Wallet for WooCommerce <= 1.4.3 takes a caller who can reach the endpoint. Authorization bypass through a user-controlled key, often called insecure direct object reference, means the application looks up a record by an identifier from the request without checking that the caller owns it.

Changing a number in the request is enough to read or modify other users' records, which on commerce and membership sites means customer data. For Wallet for WooCommerce the fix is 1.4.4: builds <= 1.4.3 are affected, anything from 1.4.4 onward is not.

Remediation

Update to version 1.4.4, 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: Wallet for WooCommerce 1.4.4 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