CartFlows <= 1.11.11 - Insecure Direct Object Reference to Arbitrary Post Deletion

2023-06-02 00:00
Anonymous

Strategic Overview

Status
Patched in 1.11.12
Affected Plugin
CartFlows – Funnel Builder & Checkout Plugin for WooCommerce
Affected Version
< 1.11.12
CVSS
2.7Low
Weakness type
CWE-639 · Authorization Bypass Through User-Controlled Key
CVE
CVE pending
View all CartFlows – Funnel Builder & Checkout Plugin for WooCommerce vulnerabilities

At a glance

This record tracks a low-severity Authorization Bypass Through User-Controlled Key vulnerability in the CartFlows WordPress plugin, affecting versions < 1.11.12. It carries a CVSS score of 2.7 (reachable over the network; low attack complexity). The issue is fixed in version 1.11.12; sites on affected versions should update now. Disclosed June 2023.

Vulnerability Overview

The CartFlows plugin for WordPress is vulnerable to Insecure Direct Object Reference in versions up to, and including, 1.11.11. This is due to the fact that during cart flow deletion/modification, the plugin does not verify that the flow ID provided to the AJAX action is indeed a cart flow id. This makes it possible for authenticated attackers, with cart flow manager access or higher, to modify or delete arbitrary posts. This permission is by default available to admins, but can be given to other user types.

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 CartFlows < 1.11.12 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 CartFlows the fix is 1.11.12: builds < 1.11.12 are affected, anything from 1.11.12 onward is not.

Remediation

Update to version 1.11.12, 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: CartFlows 1.11.12 closes this, and updating the plugin is the step that ends it.

  • Login Security
  • Alerts

External References

https://www.wordfence.com/threat-intel/vulnerabilities/id/b9002f6e-4345-4908-9cb8-9841a2458eb7

Related records

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