WPFunnels <= 2.7.15 - Insecure Direct Object Reference

2023-07-10 00:00
Anonymous

Strategic Overview

Status
Patched in 2.7.16
Affected Plugin
WPFunnels – Funnel Builder for WooCommerce with Checkout & One Click Upsell
Affected Version
< 2.7.16
CVSS
5.4Medium
Weakness type
CWE-639 · Authorization Bypass Through User-Controlled Key
CVE
CVE pending
View all WPFunnels – Funnel Builder for WooCommerce with Checkout & One Click Upsell vulnerabilities

At a glance

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

Vulnerability Overview

The WPFunnels plugin for WordPress is vulnerable to insecure direct object reference in versions up to, and including, 2.7.15. This is due to insufficient validation on a user controlled key. This makes it possible for authenticated attackers to perform actions on objects they aren't intended to manipulate.

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

Remediation

Update to version 2.7.16, 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: WPFunnels 2.7.16 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/50b26952-bf59-4236-93b4-6b4928609c15

Related records

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