Ultimate Product Catalog < 4.2.3 - Authenticated SQL Injection

2017-06-27 00:00
Lenon Leite

Strategic Overview

Status
Patched in 4.2.3
Affected Plugin
Ultimate Product Catalog
Affected Version
< 4.2.3
CVSS
5.4Medium
Weakness type
CWE-89 · Improper Neutralization of Special Elements used in an SQL Command ('SQL Injection')
CVE
CVE pending
View all Ultimate Product Catalog vulnerabilities

At a glance

This record tracks a medium-severity Improper Neutralization of Special Elements used in an SQL Command ('SQL Injection') vulnerability in the Ultimate Product Catalog WordPress plugin, affecting versions < 4.2.3. It carries a CVSS score of 5.4 (reachable over the network; low attack complexity). Exploitation requires an authenticated account. The issue is fixed in version 4.2.3; sites on affected versions should update now. Disclosed June 2017, reported by Lenon Leite.

Vulnerability Overview

The Ultimate Product Catalog plugin for WordPress is vulnerable to SQL Injection via the ‘CatID’ parameter in versions before 4.2.3 due to insufficient escaping on the user supplied parameter and lack of sufficient preparation on the existing SQL query. This makes it possible for authenticated attackers to append additional SQL queries into already existing queries that can be used to extract sensitive information from the database.

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-89: Improper Neutralization of Special Elements used in an SQL Command ('SQL Injection')

Ultimate Product Catalog < 4.2.3 carries this weakness at CatID, and reaching it takes any authenticated account. SQL injection happens when request data is concatenated into a query instead of being bound as a parameter, letting an attacker change the structure of the statement rather than just its values.

A working injection can read any table the database user can see, which on a WordPress install means user records, password hashes and session or API secrets stored in options. For Ultimate Product Catalog the fix is 4.2.3: builds < 4.2.3 are affected, anything from 4.2.3 onward is not.

Remediation

Update to version 4.2.3, or a newer patched version

How does WordSec protect against this?

The attempt arrives as an ordinary request to Ultimate Product Catalog: WordSec's web application firewall inspects request payloads before WordPress loads them. None of that substitutes for the fix: Ultimate Product Catalog 4.2.3 closes this, and updating the plugin is the step that ends it.

  • Firewall
  • Alerts

External References

https://www.wordfence.com/threat-intel/vulnerabilities/id/cb4e3b3c-20f4-4591-af0a-539b405d675e

Related records

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