dbcve.org
TerawalletWordPress extension · Standalonetech

CVE-2022-36401

HIGH · 8.8 CVSS v3.1 Published 2023-02-02
Fix available
A fix is available. Upgrade to 1.4.0 or later.
See remediation →
95/100
Remediation priority · Urgent
Remotely reachable No privileges

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
Cross-Site Request Forgery (CSRF) vulnerability in TeraWallet – For WooCommerce plugin <= 1.3.24 versions.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

Cross-Site Request Forgery (CSRF) vulnerability in the TeraWallet WooCommerce plugin allows attackers to trick authenticated users into performing unintended wallet operations (such as balance transfers, deposits, or withdrawals) by crafting malicious requests that the user's browser automatically submits due to missing or insufficient CSRF protection.

MitigationUpdate TeraWallet plugin to a version newer than 1.3.24 that includes CSRF protection, or implement anti-CSRF tokens (nonces) on all state-changing wallet operations and validate them server-side.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
TerawalletWordPress extension
Affected:< 1.4.0

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
User interaction
Required
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Confirm TeraWallet plugin is installed
    In WordPress admin, navigate to Plugins > Installed Plugins and look for 'TeraWallet' by Standalonetech, or check the wp-content/plugins/terawallet directory exists
    Affected if TeraWallet plugin is present in the WordPress installation
  2. Identify installed TeraWallet version
    In WordPress admin, go to Plugins > Installed Plugins, find TeraWallet, and note the version number displayed under the plugin name. Alternatively, check the main plugin file header in wp-content/plugins/terawallet/terawallet.php for the Version field
    Affected if The displayed version is lower than 1.4.0 (for example, 1.3.x or earlier)
  3. Verify WooCommerce is active
    In WordPress admin, confirm WooCommerce is installed and active, as TeraWallet is a WooCommerce extension that manages wallet functionality for the ecommerce platform
    Affected if WooCommerce is active and TeraWallet is enabled as a WooCommerce payment method or wallet extension

If TeraWallet plugin is installed with a version below 1.4.0 and WooCommerce is active, the site is affected by this CSRF vulnerability.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Upgrade available Upgrade to 1.4.0 or later
Fixed in 1.4.0
Interim mitigation

Update TeraWallet plugin to a version newer than 1.3.24 that includes CSRF protection, or implement anti-CSRF tokens (nonces) on all state-changing wallet operations and validate them server-side.

Recommended fix High confidence

TeraWallet – For WooCommerce version 1.4.0 or later

  1. 1. Create a full backup of your WordPress site and database before updating.
  2. 2. Navigate to WordPress admin dashboard > Plugins > Installed Plugins.
  3. 3. Locate the TeraWallet (TeraWallet – For WooCommerce) plugin in the plugin list.
  4. 4. If an update is available, click the 'Update Now' link next to the plugin, or go to Dashboard > Updates and select the plugin to update.
  5. 5. Ensure the plugin is updated to version 1.4.0 or later to address the CSRF vulnerability.
  6. 6. After updating, verify the site functions correctly and test the wallet functionality.
  7. 7. Confirm the update was successful by checking the plugin version in the Installed Plugins list.

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Terawallet Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing2.0 h
  • Review / QA1.0 h
9.0 hours of engineering $1,600
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,560.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2022-36401 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2022-36401 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data