What this page helps you verify fast
This hub clusters every indexed record for Pricing Deals for WooCommerce so operators can confirm whether a disclosed issue maps to the installed slug, version range, and patch path.
Review known vulnerability records for the WordPress plugin Pricing Deals for WooCommerce (`pricing-deals-for-woocommerce`), including severity, CVE references, affected versions, and patch status.
Recent tracked CVEs on this page include CVE-2023-41240 and CVE-2022-1057, so operators can jump from disclosure to patch validation without scanning the full feed first.
Start with the highest-signal CVE records for this WordPress plugin before scanning the full vulnerability feed.
Pricing Deals for WooCommerce <= 2.0.2.02 - Unauthenticated SQL Injection
Pricing Deals for WooCommerce <= 2.0.3.2 - Missing Authorization via vtprd_ajax_clone_rule
This hub clusters every indexed record for Pricing Deals for WooCommerce so operators can confirm whether a disclosed issue maps to the installed slug, version range, and patch path.
These recent records surface the CVE strings, patch cues, and direct report links most operators need first.
The Pricing Deals for WooCommerce plugin for WordPress is vulnerable to unauthorized modification of data| due to a missing capability check on the 'vtprd_ajax_clone_rule' function in versio...
The Pricing Deals for WooCommerce plugin for WordPress is vulnerable to SQL Injection via the 'term' parameter in versions up to, and including, 2.0.2.02 due to insufficient escaping on the...
Sorted by latest disclosure date so newly published issues surface first.
The Pricing Deals for WooCommerce plugin for WordPress is vulnerable to unauthorized modification of data| due to a missing capability check on the 'vtprd_ajax_clone_rule' function in versions up to, and including, 2.0.3.2. This makes it possible for unauthenticated attackers to...
The Pricing Deals for WooCommerce plugin for WordPress is vulnerable to SQL Injection via the 'term' parameter in versions up to, and including, 2.0.2.02 due to insufficient escaping on the user supplied parameter and lack of sufficient preparation on the existing SQL query. This...