CVE-2021-24952

Conversios.io - Google Analytics and Google Shopping plugin for WooCommerce <= 4.6.1 Authenticated SQL Injection

2022-02-01 00:00
ZhongFu Su

Strategic Overview

Status
Patched in 4.6.2
Affected Version
< 4.6.2
CVSS
8.8High
Weakness type
CWE-89 · Improper Neutralization of Special Elements used in an SQL Command ('SQL Injection')
CVE
CVE-2021-24952
View all Conversios – GA4, Google Ads & Meta Conversion Tracking with Product Feed for WooCommerce vulnerabilities

At a glance

CVE-2021-24952 is a high-severity Improper Neutralization of Special Elements used in an SQL Command ('SQL Injection') vulnerability in the Conversios WordPress plugin, affecting versions < 4.6.2. It carries a CVSS score of 8.8 (reachable over the network; low attack complexity; high confidentiality, integrity, availability impact). Exploitation requires an authenticated account. The issue is fixed in version 4.6.2; sites on affected versions should update now. Disclosed February 2022, reported by ZhongFu Su.

Vulnerability Overview

The Conversios.io WordPress plugin before 4.6.2 does not sanitise, validate and escape the sync_progressive_data parameter for the tvcajax_product_sync_bantch_wise AJAX action before using it in a SQL statement, allowing any authenticated user to perform SQL injection attacks.

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')

Reaching this weakness in Conversios < 4.6.2 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 Conversios the fix is 4.6.2: builds < 4.6.2 are affected, anything from 4.6.2 onward is not.

Remediation

Update to version 4.6.2, or a newer patched version

How does WordSec protect against this?

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

  • Firewall
  • Alerts

External References

Related records

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