CVE-2021-24846

Ni WooCommerce Custom Order Status <= 1.9.6 - SQL Injection

2021-11-22 00:00
ZhongFu Su

Strategic Overview

Status
Patched in 1.9.7
Affected Version
<= 1.9.6
CVSS
8.8High
Weakness type
CWE-89 · Improper Neutralization of Special Elements used in an SQL Command ('SQL Injection')
CVE
CVE-2021-24846
View all Ni WooCommerce Custom Order Status vulnerabilities

At a glance

CVE-2021-24846 is a high-severity Improper Neutralization of Special Elements used in an SQL Command ('SQL Injection') vulnerability in the Ni WooCommerce Custom Order Status WordPress plugin, affecting versions <= 1.9.6. 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 1.9.7; sites on affected versions should update now. Disclosed November 2021, reported by ZhongFu Su.

Vulnerability Overview

The get_query() function of the Ni WooCommerce Custom Order Status WordPress plugin before 1.9.7, used by the niwoocos_ajax AJAX action, available to all authenticated users, does not properly sanitise the sort parameter before using it in a SQL statement, leading to an SQL injection, exploitable by any authenticated users, such as subscriber

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

Ni WooCommerce Custom Order Status <= 1.9.6 carries this weakness at get_query(), and reaching it takes a caller who can reach the endpoint. 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 Ni WooCommerce Custom Order Status the fix is 1.9.7: builds <= 1.9.6 are affected, anything from 1.9.7 onward is not.

Remediation

Update to version 1.9.7, or a newer patched version

How does WordSec protect against this?

The attempt arrives as an ordinary request to Ni WooCommerce Custom Order Status: WordSec's web application firewall inspects request payloads before WordPress loads them. None of that substitutes for the fix: Ni WooCommerce Custom Order Status 1.9.7 closes this, and updating the plugin is the step that ends it.

  • Firewall
  • Alerts

External References

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