dbcve.org
SQL InjectionWeakness · CWE-89

CVE-2025-47640

CRITICAL · 9.3 CVSS v3.1 Published 2025-05-23
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable No privileges 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 printcart Printcart Web to Print Product Designer for WooCommerce printcart-integration allows SQL Injection.This issue affects Printcart Web to Print Product Designer for WooCommerce: from n/a through <= 2.4.0.

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

SQL injection vulnerability in the Printcart Web to Print Product Designer for WooCommerce plugin (printcart-integration component) allows attackers to inject malicious SQL commands through unsanitized user input, potentially enabling unauthorized database access, data exfiltration, or complete system compromise.

MitigationUpdate the Printcart plugin to a version beyond 2.4.0 that includes proper input sanitization and parameterized queries, or apply vendor-supplied security patches; if immediate patching is unavailable, restrict administrative access and implement database query monitoring for suspicious activity.

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

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:N/A:L

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. Confirm Printcart plugin is installed
    Access WordPress admin dashboard, go to Plugins > Installed Plugins, and search for 'Printcart' or 'Web to Print Product Designer'. Alternatively, check the wp-content/plugins/ directory for a folder named 'printcart' or similar.
    Affected if The Printcart Web to Print Product Designer for WooCommerce plugin is found in the WordPress installation
  2. Identify the installed plugin version
    In WordPress admin, click on the Printcart plugin to view its details and version number. Alternatively, open the main plugin PHP file (usually printcart.php or similar in the plugin folder) and locate the 'Version:' header in the plugin comments, or check readme.txt for the version tag.
    Affected if The installed version is 2.4.0 or lower (versions up to and including 2.4.0 are affected)
  3. Verify the printcart-integration component is active
    Check WordPress admin under the Printcart plugin settings or WooCommerce > Printcart settings to confirm the 'printcart-integration' component or module is enabled. This component handles the user input that is vulnerable to SQL injection.
    Affected if The printcart-integration component is enabled in the plugin configuration
  4. Inspect network requests for vulnerable parameters
    If you have access to server logs or a web application firewall, review incoming requests for the printcart-integration endpoint. Look for parameters that may be passed to the database unsanitized. In a test environment, submit a benign SQL injection test string (e.g., a single quote) to any Printcart public-facing form or API endpoint and monitor for SQL errors.
    Affected if User-supplied input in Printcart forms or API calls reaches database queries without proper sanitization, resulting in SQL errors or unexpected behavior

A user is affected if the Printcart Web to Print Product Designer plugin version is 2.4.0 or lower AND the printcart-integration component is enabled, allowing unsanitized user input to reach SQL queries.

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

Update the Printcart plugin to a version beyond 2.4.0 that includes proper input sanitization and parameterized queries, or apply vendor-supplied security patches; if immediate patching is unavailable, restrict administrative access and implement database query monitoring for suspicious activity.

Have this fixed Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing4.0 h
  • Review / QA2.0 h
15.0 hours of engineering $2,640
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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