CVE-2023-40559
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedCross-Site Request Forgery (CSRF) vulnerability in theDotstore Dynamic Pricing and Discount Rules for WooCommerce plugin <= 2.4.0 versions.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · moderate confidenceCross-Site Request Forgery (CSRF) vulnerability in theDotstore Dynamic Pricing and Discount Rules for WooCommerce plugin versions 2.4.0 and below allows attackers to induce authenticated administrators to perform unintended actions such as modifying pricing rules or discount configurations.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data< 2.4.1CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- None
- User interaction
- Required
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Locate the plugin installationCheck your WordPress plugins directory (wp-content/plugins/) for a folder containing 'dynamic-pricing-discount-rules-for-woocommerce', 'multidots', or 'thedotstore' in the name. Alternatively, log into WordPress admin and navigate to Plugins > Installed Plugins to find 'Dynamic Pricing And Discount Rules For Woocommerce' or similar.Affected if The plugin is present in your WordPress installation.
-
Identify the installed versionIn WordPress admin, go to Plugins > Installed Plugins and find the plugin. The version number is displayed below the plugin name. Alternatively, inspect the plugin's main PHP file (usually in the plugin folder root) and look for a 'Version' header in the plugin comment block.Affected if The version displayed is 2.4.0 or lower, meaning it is less than 2.4.1.
-
Confirm the vendor and product nameVerify the plugin is developed by 'Multidots' or 'theDotstore' and is specifically the 'Dynamic Pricing And Discount Rules For Woocommerce' plugin, as other similar-named plugins from different vendors may not be affected.Affected if The plugin matches both the vendor (Multidots/theDotstore) and the specific product name.
You are affected if the Multidots Dynamic Pricing And Discount Rules For WooCommerce plugin version 2.4.0 or lower is installed and active on your WordPress site, and administrators can authenticate to the WordPress admin area.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
dbcve · scoped2.4.1
Update the plugin to the latest version > 2.4.0 which should include proper anti-CSRF token validation, or implement nonce verification on all state-changing admin actions if no patch is available.
2.4.1
- Navigate to WordPress admin dashboard > Plugins > Installed Plugins
- Locate 'Dynamic Pricing and Discount Rules for WooCommerce' in the plugins list
- If an update is available, click 'Update now' to upgrade to version 2.4.1 or later
- Alternatively, download version 2.4.1 or the latest version from the WordPress plugin repository and upload it manually
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation3.0 h
- Implementation8.0 h
- Testing4.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,800.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2023-40559 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2023-40559 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data