CVE-2021-4395

Abandoned Cart Recovery for WooCommerce <= 1.0.4 - Cross-Site Request Forgery Bypass

2021-07-05 00:00
Jerome Bruandet

Strategic Overview

Status
Patched in 1.0.4.1
Affected Version
<= 1.0.4
CVSS
4.3Medium
Weakness type
CWE-352 · Cross-Site Request Forgery (CSRF)
CVE
CVE-2021-4395
View all Recarto – Abandoned Cart Recovery for WooCommerce vulnerabilities

At a glance

CVE-2021-4395 is a medium-severity Cross-Site Request Forgery (CSRF) vulnerability in the Recarto WordPress plugin, affecting versions <= 1.0.4. 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.0.4.1; sites on affected versions should update now. Disclosed July 2021, reported by Jerome Bruandet.

Vulnerability Overview

The Abandoned Cart Recovery for WooCommerce plugin for WordPress is vulnerable to Cross-Site Request Forgery in versions up to, and including, 1.0.4. This is due to missing or incorrect nonce validation on the get_items() and extra_tablenav() functions. This makes it possible for unauthenticated attackers to perform read-only actions 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)

Recarto <= 1.0.4 carries this weakness at get_items(), and reaching it 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 Recarto the fix is 1.0.4.1: builds <= 1.0.4 are affected, anything from 1.0.4.1 onward is not.

Remediation

Update to version 1.0.4.1, or a newer patched version

How does WordSec protect against this?

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

  • Firewall
  • Alerts

External References

Related records

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