TeraWallet – For WooCommerce <= 1.3.24 - Cross-Site Request Forgery via admin_options
Strategic Overview
- Status
- Patched in 1.4.0
- Affected Plugin
- Wallet for WooCommerce
- Affected Version
<= 1.3.24- CVSS
- 4.3Medium
- Weakness type
- CWE-352 · Cross-Site Request Forgery (CSRF)
- CVE
CVE-2022-40198
At a glance
CVE-2022-40198 is a medium-severity Cross-Site Request Forgery (CSRF) vulnerability in the Wallet for WooCommerce WordPress plugin, affecting versions <= 1.3.24. 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 1.4.0; sites on affected versions should update now. Disclosed February 2023, reported by Muhammad Daffa.
Vulnerability Overview
The TeraWallet plugin for WordPress is vulnerable to Cross-Site Request Forgery in versions up to, and including, 1.3.24. This is due to missing nonce validation on the admin_options function. This makes it possible for unauthenticated attackers to modify plugin settings, 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)
Reaching this weakness in Wallet for WooCommerce <= 1.3.24 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 Wallet for WooCommerce the fix is 1.4.0: builds <= 1.3.24 are affected, anything from 1.4.0 onward is not.
Remediation
Update to version 1.4.0, or a newer patched version
How does WordSec protect against this?
The attempt arrives as an ordinary request to Wallet for WooCommerce: WordSec's web application firewall inspects request payloads before WordPress loads them. None of that substitutes for the fix: Wallet for WooCommerce 1.4.0 closes this, and updating the plugin is the step that ends it.
- Firewall
- Alerts
External References
Related records
Same weakness class
Other vulnerabilities in Wallet for WooCommerce
- 8.8CVE-2024-6353: Wallet for WooCommerce <= 1.5.4 SQL Injection
CVE-2024-6353 - 6.5CVE-2024-7747: Wallet for WooCommerce Incorrect Conversion between
CVE-2024-7747 - 4.4CVE-2024-32584: TeraWallet Stored XSS
CVE-2024-32584 - 4.3CVE-2026-16538: TeraWallet - Wallet… Authenticated (Subscriber+)
CVE-2026-16538 - 4.3CVE-2026-12103: Wallet for WooCommerce Authenticated (Subscriber+)
CVE-2026-12103 - 4.3CVE-2026-32398: TeraWallet – For WooCommerce <= 1.5.15 Race Condition
CVE-2026-32398 - 4.3CVE-2024-1690: TeraWallet Authenticated (Subscriber+) User Email
CVE-2024-1690 - 4.3CVE-2022-3995: TeraWallet – For WooCommerce <= 1.4.3 IDOR
CVE-2022-3995
Vulnerability data © Defiant, Inc., provided under the Wordfence Intelligence T&C