CVE-2019-16251

YIT Plugin Framework <= 3.3.8 - Authenticated Settings Change

2019-10-31 00:00
Jerome Bruandet

Strategic Overview

Status
Patched in 2.2.14
Affected Version
<= 2.2.13
CVSS
4.3Medium
Weakness type
CWE-862 · Missing Authorization
CVE
CVE-2019-16251
View all YITH WooCommerce Wishlist vulnerabilities

At a glance

CVE-2019-16251 is a medium-severity Missing Authorization vulnerability in the YITH WooCommerce Wishlist WordPress plugin, affecting versions <= 2.2.13. It carries a CVSS score of 4.3 (reachable over the network; low attack complexity). Exploitation requires an authenticated account. The issue is fixed in version 2.2.14; sites on affected versions should update now. Disclosed October 2019, reported by Jerome Bruandet.

Vulnerability Overview

Various versions of a various YITH WooCommerce plugins that use the YIT Plugin Framework through 3.3.8 are vulnerable to authorization bypass due to a missing capability check in the the 'save_toggle_element_options' function in .plugin-fw/lib/yit-plugin-panel-wc.php. This allows authenticated users with subscriber-level permissions or above to change arbitrary plugin settings.

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-862: Missing Authorization

YITH WooCommerce Wishlist <= 2.2.13 carries this weakness at save_toggle_element_options, and reaching it takes any authenticated account. A missing authorization check means a function is reachable by anyone who can reach the endpoint, because the code never asks whether the caller is allowed to perform the action.

Any user who can reach the endpoint gets to run an action reserved for higher-privileged roles, from reading protected data to changing settings or content. For YITH WooCommerce Wishlist the fix is 2.2.14: builds <= 2.2.13 are affected, anything from 2.2.14 onward is not.

Remediation

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

  • Login Security
  • Alerts

External References

Related records

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