dbcve.org
Code InjectionWeakness · CWE-94

CVE-2025-47588

CRITICAL · 9.1 CVSS v3.1 Published 2025-11-06
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
97/100
Remediation priority · Urgent
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 Control of Generation of Code ('Code Injection') vulnerability in acowebs Dynamic Pricing With Discount Rules for WooCommerce aco-woo-dynamic-pricing allows Code Injection.This issue affects Dynamic Pricing With Discount Rules for WooCommerce: from n/a through <= 4.5.9.

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 confidence

Code injection vulnerability in the aco-woo-dynamic-pricing WordPress plugin (Dynamic Pricing With Discount Rules for WooCommerce) allows attackers to inject malicious code through improper control of code generation. The vulnerability affects versions up to and including 4.5.9. The CVSS 9.1 score indicates this is likely an unauthenticated attack vector with complete system compromise potential.

MitigationUpgrade to the latest version of the plugin immediately. If no patched version exists, consider disabling the plugin until a fix is available, and implement WAF rules to block suspicious input patterns targeting the plugin's endpoints.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

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
Changed
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:C/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. Locate the plugin in WordPress installation
    Access the WordPress admin dashboard, navigate to Plugins > Installed Plugins, and look for 'Dynamic Pricing With Discount Rules for WooCommerce' or 'aco-woo-dynamic-pricing'. Alternatively, check the /wp-content/plugins/ directory for a folder named 'aco-woo-dynamic-pricing' or similar dynamic pricing plugin folders.
    Affected if The plugin folder exists in the WordPress plugins directory.
  2. Determine installed plugin version
    In WordPress admin, click on the plugin from the Installed Plugins list to view its details, or inspect the main plugin PHP file (usually in the plugin root folder) for a version constant or header comment. Check the plugin's main file for a line like 'Version: x.x.x' or a defined constant containing the version number.
    Affected if The displayed version is 4.5.9 or lower.
  3. Identify plugin entry points
    Review the plugin's PHP files for functions handling user input that could be used for code generation. Look for files in includes/ or classes/ directories, particularly any handling $_GET, $_POST, or $_REQUEST parameters. Search for eval(), include(), require(), or similar dynamic code execution functions.
    Affected if The plugin contains endpoints that process unsanitized user input and the version is 4.5.9 or lower.
  4. Check web server logs for exploitation attempts
    Review web server access logs (Apache access_log, Nginx access.log) for requests to the plugin's PHP files with suspicious patterns such as encoded characters, shell commands, or code injection payloads targeting known plugin endpoints.
    Affected if Logs show requests to plugin files containing code injection patterns and the plugin version is 4.5.9 or lower.
  5. Verify WordPress REST API exposure
    Check if the plugin registers custom REST API routes by accessing /wp-json/ and examining the response for any endpoints related to dynamic pricing, discounts, or pricing rules. Also check /wp-json/wp/v2/routes or similar.
    Affected if The plugin exposes REST API endpoints and the version is 4.5.9 or lower.

If the aco-woo-dynamic-pricing plugin is installed with version 4.5.9 or lower and exposes endpoints that accept user-controlled input for dynamic code generation, the environment is affected by CVE-2025-47588.

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.

From vendor data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Upgrade to the latest version of the plugin immediately. If no patched version exists, consider disabling the plugin until a fix is available, and implement WAF rules to block suspicious input patterns targeting the plugin's endpoints.

Have this fixed Scoped from the published advisory
  • Consultation4.0 h
  • Implementation12.0 h
  • Testing16.0 h
  • Review / QA6.0 h
38.0 hours of engineering $6,440
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-47588 — 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-47588 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