dbcve.org
Dynamic Pricing With Discount Rules For WoocommerceWordPress extension · Acowebs

CVE-2025-47544

HIGH · 7.2 CVSS v3.1 Published 2025-05-07
Fix available
A fix is available. Upgrade to 4.5.9 or later.
See remediation →
78/100
Remediation priority · High
Remotely reachable Zero-click

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 · unedited
Improper Neutralization of Special Elements used in an SQL Command ('SQL Injection') vulnerability in acowebs Dynamic Pricing With Discount Rules for WooCommerce aco-woo-dynamic-pricing allows Blind SQL Injection.This issue affects Dynamic Pricing With Discount Rules for WooCommerce: from n/a through <= 4.5.8.

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 · high confidence

A blind SQL injection vulnerability exists in the acowebs Dynamic Pricing With Discount Rules for WooCommerce plugin (aco-woo-dynamic-pricing) versions through 4.5.8. The vulnerability allows unauthenticated attackers to inject malicious SQL queries through unsanitized input parameters in the plugin's pricing functionality.

MitigationApply vendor patch/update when available. As an interim measure, consider deploying a WAF rule to block SQL injection patterns and restrict access to the affected endpoint.

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
Dynamic Pricing With Discount Rules For WoocommerceWordPress extension
Affected:< 4.5.9

CVSS 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
High
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:H/UI:N/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 checks

Work through these to decide whether this CVE applies to you.

  1. Verify plugin version
    Navigate to WordPress admin > Plugins > Installed Plugins > Acowebs Dynamic Pricing With Discount Rules For Woocommerce and note the version number displayed. Alternatively, check the plugin's main PHP file (typically in wp-content/plugins/aco-woo-dynamic-pricing/) for the version defined in the plugin header comment.
    Affected if The displayed version is 4.5.8 or lower (any version prior to 4.5.9)
  2. Confirm plugin is active
    In WordPress admin > Plugins > Installed Plugins, verify whether the 'Acowebs Dynamic Pricing With Discount Rules For Woocommerce' plugin is currently activated.
    Affected if The plugin is active and the version is 4.5.8 or lower
  3. Check for pricing rule configuration
    In the WordPress admin panel, locate the plugin menu (typically under WooCommerce > Dynamic Pricing or similar) and check if any pricing rules or discount rules have been created and enabled.
    Affected if Pricing rules are configured and the plugin version is vulnerable (4.5.8 or lower)
  4. Inspect HTTP requests to pricing endpoint
    Use browser developer tools or a proxy (such as Burp Suite or OWASP ZAP) to monitor HTTP requests when interacting with the cart or product pages. Identify any POST/GET parameters being sent to the plugin's pricing functionality (commonly related to price calculation or discount application).
    Affected if Unsanitized parameters are observed in requests to the plugin's pricing functionality and the plugin version is 4.5.8 or lower

If the installed plugin version is 4.5.8 or lower (any version through 4.5.8), the site is vulnerable to unauthenticated blind SQL injection via the plugin's pricing input parameters.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 · scoped
Upgrade available Upgrade to 4.5.9 or later
Fixed in 4.5.9
Interim mitigation

Apply vendor patch/update when available. As an interim measure, consider deploying a WAF rule to block SQL injection patterns and restrict access to the affected endpoint.

Recommended fix High confidence

4.5.9

  1. Backup your WordPress site and database before updating
  2. Navigate to WordPress admin dashboard > Plugins
  3. Find 'Dynamic Pricing With Discount Rules for WooCommerce' plugin
  4. Click 'Update now' to upgrade to version 4.5.9 or later
  5. Alternatively, download version 4.5.9+ from the WordPress plugin repository and upload manually
  6. After updating, clear any caching mechanisms
  7. Verify the plugin shows version 4.5.9 or higher in the plugins list

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Dynamic Pricing With Discount Rules For Woocommerce Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing4.0 h
  • Review / QA2.0 h
18.0 hours of engineering $3,200
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,120.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-47544 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2025-47544 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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