Ultimate Product Catalog <= 3.8.1 - Missing Authorization to Plugin Settings Update

2016-06-17 00:00
Joaquin Ramirez Martinez

Strategic Overview

Status
Patched in 3.8.2
Affected Plugin
Ultimate Product Catalog
Affected Version
< 3.8.2
CVSS
4.3Medium
Weakness type
CWE-862 · Missing Authorization
CVE
CVE pending
View all Ultimate Product Catalog vulnerabilities

At a glance

This record tracks a medium-severity Missing Authorization vulnerability in the Ultimate Product Catalog WordPress plugin, affecting versions < 3.8.2. It carries a CVSS score of 4.3 (reachable over the network; low attack complexity). The root cause is a missing authorization check on a reachable function. The issue is fixed in version 3.8.2; sites on affected versions should update now. Disclosed June 2016, reported by Joaquin Ramirez Martinez.

Vulnerability Overview

The Ultimate Product Catalog plugin for WordPress is vulnerable to authorization bypass due to a missing capability check on the Update_UPCP_Options() function in versions up to, and including, 3.8.1. This makes it possible for authenticated attackers, with contributor-level permissions and above, to edit 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

Ultimate Product Catalog < 3.8.2 carries this weakness at Update_UPCP_Options(), and reaching it takes a caller who can reach the endpoint. 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 Ultimate Product Catalog the fix is 3.8.2: builds < 3.8.2 are affected, anything from 3.8.2 onward is not.

Remediation

Update to version 3.8.2, 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: Ultimate Product Catalog 3.8.2 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/2cff84a4-9264-4789-997b-bc11a8bac449

Related records

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