WordPress security by component
Product Feed PRO for WooCommerce
Plugin description
Product Feed PRO for WooCommerce is a WordPress component with 4 published CVE records in this archive. The latest tracked vulnerability was published Mar 13, 2026; the highest CVE/CNA score is 7.1.
Plugin slug:
woo-product-feed-proLatest vulnerability
CVE-2026-32443: Product Feed PRO for WooCommerce: Cross-site request forgery
Product Feed PRO for WooCommerce is affected by cross-site request forgery. Exposure depends on how the affected operation is made reachable by the site. Exploitation relies on a signed-in privileged user submitting an attacker-controlled request.
| Safe version |
|
||
|---|---|---|---|
| Mar 13, 2026 |
CVE-2026-32443
Product Feed PRO for WooCommerce: Cross-site request forgery
Product Feed PRO for WooCommerce is affected by cross-site request forgery. Exposure depends on how the affected operation is made reachable by the site. Exploitation relies on a signed-in privileged user submitting an attacker-controlled request.
|
See mitigation notes |
CVE6.5
NVDPending
|
| Apr 17, 2024 |
CVE-2024-32513
Product Feed PRO for WooCommerce: A security weakness
Product Feed PRO for WooCommerce is affected by a security weakness. Exposure depends on how the affected operation is made reachable by the site. The resulting impact depends on how the affected component exposes the vulnerable operation.
|
See mitigation notes |
CVE5.3
NVDPending
|
| Mar 27, 2024 |
CVE-2024-24800
Product Feed PRO for WooCommerce: Cross-site scripting
Product Feed PRO for WooCommerce is affected by cross-site scripting. Exposure depends on how the affected operation is made reachable by the site. Injected script can execute in the affected site's origin when the vulnerable output is viewed.
|
See mitigation notes |
CVE7.1
NVDPending
|
| Apr 06, 2023 |
CVE-2022-46793
Woo Product Feed Pro: Cross-site request forgery
Woo Product Feed Pro is affected by cross-site request forgery. Exposure depends on how the affected operation is made reachable by the site. Exploitation relies on a signed-in privileged user submitting an attacker-controlled request.
|
See mitigation notes |
CVE5.4
NVD8.8
|