CVE-2024-13682

Wallet System for WooCommerce – Wallet, Wallet Cashback, Refunds, Partial Payment, Wallet Restriction <= 2.6.2 - Cross-Site Request Forgery

2025-03-03 20:19
Tim Coen

Strategic Overview

Status
Patched in 2.6.3
Affected Plugin
Wallet System for WooCommerce – Digital Wallet, Buy Now Pay Later (BNPL), Instant Cashback, Referral program, Partial & Subscription Payments
Affected Version
<= 2.6.2
CVSS
4.3Medium
Weakness type
CWE-352 · Cross-Site Request Forgery (CSRF)
CVE
CVE-2024-13682
View all Wallet System for WooCommerce – Digital Wallet, Buy Now Pay Later (BNPL), Instant Cashback, Referral program, Partial & Subscription Payments vulnerabilities

At a glance

CVE-2024-13682 is a medium-severity Cross-Site Request Forgery (CSRF) vulnerability in the Wallet System for WooCommerce WordPress plugin, affecting versions <= 2.6.2. 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 2.6.3; sites on affected versions should update now. Disclosed March 2025, reported by Tim Coen.

Vulnerability Overview

The Wallet System for WooCommerce – Wallet, Wallet Cashback, Refunds, Partial Payment, Wallet Restriction plugin for WordPress is vulnerable to Cross-Site Request Forgery in all versions up to, and including, 2.6.2. This is due to missing or incorrect nonce validation in class-wallet-user-table.php. This makes it possible for unauthenticated attackers to modify wallet balances via a 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 System for WooCommerce <= 2.6.2 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 System for WooCommerce the fix is 2.6.3: builds <= 2.6.2 are affected, anything from 2.6.3 onward is not.

Remediation

Update to version 2.6.3, or a newer patched version

How does WordSec protect against this?

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

  • Firewall
  • Alerts

External References

https://www.cve.org/CVERecord?id=CVE-2024-13682https://www.wordfence.com/threat-intel/vulnerabilities/id/779a9f7a-4582-4d5e-bd9a-9ff7f14b452ahttps://nvd.nist.gov/vuln/detail/CVE-2024-13682

Related records

Other vulnerabilities in Wallet System for WooCommerce – Digital Wallet, Buy Now Pay Later (BNPL), Instant Cashback, Referral program, Partial & Subscription Payments

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