Ultimate Product Catalog <= 4.2.21 - Authorization Bypass and Cross-Site Request Forgery

2017-10-03 00:00
Anonymous

Strategic Overview

Status
Patched in 4.2.22
Affected Plugin
Ultimate Product Catalog
Affected Version
<= 4.2.21
CVSS
8.8High
Weakness type
CWE-862 · Missing Authorization
CVE
CVE pending
View all Ultimate Product Catalog vulnerabilities

At a glance

This record tracks a high-severity Missing Authorization vulnerability in the Ultimate Product Catalog WordPress plugin, affecting versions <= 4.2.21. It carries a CVSS score of 8.8 (reachable over the network; low attack complexity; high confidentiality, integrity, availability impact). The issue is fixed in version 4.2.22; sites on affected versions should update now. Disclosed October 2017.

Vulnerability Overview

The Ultimate Product Catalog plugin for WordPress is vulnerable to authorization bypass and Cross-Site Request Forgery in versions up to, and including 4.2.21 due to missing capability and nonce checking on various functions. This makes it possible for authenticated attackers to perform a wide variety of actions such as updating the plugin's settings and uploading arbitrary files.

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. A successful exploit has high impact on confidentiality, integrity, availability — full site compromise territory.

CWE-862: Missing Authorization

Reaching this weakness in Ultimate Product Catalog <= 4.2.21 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 4.2.22: builds <= 4.2.21 are affected, anything from 4.2.22 onward is not.

Remediation

Update to version 4.2.22, 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 4.2.22 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/edcc23e0-075a-47e6-979d-7e75eed4337d

Related records

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