Product Feed on WooCommerce for Google, Awin, Shareasale, Bing, and More < 3.3.1.0 - Authenticated SQL Injection via product_id Parameter
Strategic Overview
- Status
- Patched in 3.3.1.0
- Affected Version
< 3.3.1.0- CVSS
- 7.2High
- Weakness type
- CWE-89 · Improper Neutralization of Special Elements used in an SQL Command ('SQL Injection')
- CVE
CVE-2021-24511
At a glance
CVE-2021-24511 is a high-severity Improper Neutralization of Special Elements used in an SQL Command ('SQL Injection') vulnerability in the Product Feed on WooCommerce for Google, Awin, Shareasale, Bing, and More WordPress plugin, affecting versions < 3.3.1.0. It carries a CVSS score of 7.2 (reachable over the network; low attack complexity; high confidentiality, integrity, availability impact). Exploitation requires an authenticated account. The issue is fixed in version 3.3.1.0; sites on affected versions should update now. Disclosed August 2021, reported by Syed Sheeraz Ali.
Vulnerability Overview
The fetch_product_ajax functionality in the Product Feed on WooCommerce WordPress plugin before 3.3.1.0 uses a `product_id` POST parameter which is not properly sanitised, escaped or validated before inserting to a SQL statement, leading to SQL injection.
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 Product Feed on WooCommerce for Google, Awin, Shareasale, Bing, and More < 3.3.1.0 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 Product Feed on WooCommerce for Google, Awin, Shareasale, Bing, and More the fix is 3.3.1.0: builds < 3.3.1.0 are affected, anything from 3.3.1.0 onward is not.
Remediation
Update to version 3.3.1.0, or a newer patched version
How does WordSec protect against this?
The attempt arrives as an ordinary request to Product Feed on WooCommerce for Google, Awin, Shareasale, Bing, and More: WordSec's web application firewall inspects request payloads before WordPress loads them. None of that substitutes for the fix: Product Feed on WooCommerce for Google, Awin, Shareasale, Bing, and More 3.3.1.0 closes this, and updating the plugin is the step that ends it.
- Firewall
- Alerts
External References
Related records
Same weakness class
Other vulnerabilities in Product Feed on WooCommerce for Google, Awin, Shareasale, Bing, and More
Vulnerability data © Defiant, Inc., provided under the Wordfence Intelligence T&C