GG Woo Feed for WooCommerce Shopping Feed <= 1.2.6 - Missing Authorization
Strategic Overview
- Status
- Patched in 1.2.7
- Affected Version
<= 1.2.6- CVSS
- 4.3Medium
- Weakness type
- CWE-862 · Missing Authorization
- CVE
CVE-2024-32519
At a glance
CVE-2024-32519 is a medium-severity Missing Authorization vulnerability in the GG Woo Feed for WooCommerce Shopping Feed on Google and Other Channels WordPress plugin, affecting versions <= 1.2.6. It carries a CVSS score of 4.3 (reachable over the network; low attack complexity). The root cause is a missing authorization check on a reachable function. The issue is fixed in version 1.2.7; sites on affected versions should update now. Disclosed April 2024, reported by Abdi Pranata.
Vulnerability Overview
The GG Woo Feed for WooCommerce Shopping Feed on Google Facebook and Other Channels plugin for WordPress is vulnerable to unauthorized modification of data due to missing capability checks on several functions in the /inc/Core/ajax-functions.php file in all versions up to, and including, 1.2.6. This makes it possible for authenticated attackers, with subscriber-level access and above, to perform several unauthorized actions.
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-862: Missing Authorization
Reaching this weakness in GG Woo Feed for WooCommerce Shopping Feed on Google and Other Channels <= 1.2.6 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 GG Woo Feed for WooCommerce Shopping Feed on Google and Other Channels the fix is 1.2.7: builds <= 1.2.6 are affected, anything from 1.2.7 onward is not.
Remediation
Update to version 1.2.7, 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: GG Woo Feed for WooCommerce Shopping Feed on Google and Other Channels 1.2.7 closes this, and updating the plugin is the step that ends it.
- Login Security
- Alerts
External References
Related records
Vulnerability data © Defiant, Inc., provided under the Wordfence Intelligence T&C