Title: Security vulnerability alert
Last modified: August 22, 2023

---

# Security vulnerability alert

 *  Resolved [cfm168](https://wordpress.org/support/users/cfm168/)
 * (@cfm168)
 * [2 years, 9 months ago](https://wordpress.org/support/topic/security-vulnerability-alert/)
 * Hello, I received following security risk warning:
 * —————————————————————————
 * Input validation vulnerability in Dynamic Pricing and Discount Rules for WooCommerce
   2.4.0
   CVE-2023-40559Severity: medium-riskStatus: OpenPublication: August 16, 
   2023The WooCommerce Dynamic Pricing and Discount Rules plugin for WordPress has
   a security vulnerability in versions up to and including 2.4.0. This vulnerability
   is due to a lack of nonce validation on several functions, which means that malicious
   attackers can control the plugin’s settings by sending a false request, as long
   as they can trick a site
 * ————————————————————————–
 * I am running Woocomerce v8.0.2, WP6.3.
 * Can you possible to fix it? Thanks in advance!

Viewing 6 replies - 1 through 6 (of 6 total)

 *  Plugin Support [Hitendra Chopda](https://wordpress.org/support/users/hitendra-chopda/)
 * (@hitendra-chopda)
 * [2 years, 9 months ago](https://wordpress.org/support/topic/security-vulnerability-alert/#post-16995547)
 * Hello [@cfm168](https://wordpress.org/support/users/cfm168/),
 * Thanks for reaching.
 * We are working on the security points and will release a new version with the
   security patch.
 * Best Regards,
   Hitendra & Dotstore Team
 *  Thread Starter [cfm168](https://wordpress.org/support/users/cfm168/)
 * (@cfm168)
 * [2 years, 9 months ago](https://wordpress.org/support/topic/security-vulnerability-alert/#post-17034731)
 * Any updates?
 *  Plugin Support [Hitendra Chopda](https://wordpress.org/support/users/hitendra-chopda/)
 * (@hitendra-chopda)
 * [2 years, 9 months ago](https://wordpress.org/support/topic/security-vulnerability-alert/#post-17034752)
 * Thanks for the followup.
 * The testing is almost finished, and it will be released next week.
 * Best,
   Hitendra & Dotstore Team
 *  Plugin Support [Hitendra Chopda](https://wordpress.org/support/users/hitendra-chopda/)
 * (@hitendra-chopda)
 * [2 years, 8 months ago](https://wordpress.org/support/topic/security-vulnerability-alert/#post-17058160)
 * Hello [@cfm168](https://wordpress.org/support/users/cfm168/)
 * Please update the plugin version to resolve your query.
 * Best Regards,
   Hitendra & Dotstore Team
 *  Thread Starter [cfm168](https://wordpress.org/support/users/cfm168/)
 * (@cfm168)
 * [2 years, 8 months ago](https://wordpress.org/support/topic/security-vulnerability-alert/#post-17059896)
 * I already have the Version 2.4.1. Thanks!
 *  Plugin Support [Hitendra Chopda](https://wordpress.org/support/users/hitendra-chopda/)
 * (@hitendra-chopda)
 * [2 years, 8 months ago](https://wordpress.org/support/topic/security-vulnerability-alert/#post-17067572)
 * Thanks for the upgrade!

Viewing 6 replies - 1 through 6 (of 6 total)

The topic ‘Security vulnerability alert’ is closed to new replies.

 * ![](https://ps.w.org/woo-conditional-discount-rules-for-checkout/assets/icon-
   256x256.png?rev=3011371)
 * [Dynamic Pricing and Discount Rules for WooCommerce](https://wordpress.org/plugins/woo-conditional-discount-rules-for-checkout/)
 * [Frequently Asked Questions](https://wordpress.org/plugins/woo-conditional-discount-rules-for-checkout/#faq)
 * [Support Threads](https://wordpress.org/support/plugin/woo-conditional-discount-rules-for-checkout/)
 * [Active Topics](https://wordpress.org/support/plugin/woo-conditional-discount-rules-for-checkout/active/)
 * [Unresolved Topics](https://wordpress.org/support/plugin/woo-conditional-discount-rules-for-checkout/unresolved/)
 * [Reviews](https://wordpress.org/support/plugin/woo-conditional-discount-rules-for-checkout/reviews/)

 * 6 replies
 * 2 participants
 * Last reply from: [Hitendra Chopda](https://wordpress.org/support/users/hitendra-chopda/)
 * Last activity: [2 years, 8 months ago](https://wordpress.org/support/topic/security-vulnerability-alert/#post-17067572)
 * Status: resolved