SQL InjectionWeakness · CWE-89

CVE-2025-24780

HIGH · 8.5 CVSS v3.1 Published 2025-07-04

Mitigation only

No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.

See remediation →

91/100

Remediation priority · Urgent

Remotely reachable Zero-click

Official description

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

dbcve analysis · moderate confidence

SQL injection vulnerability in the printcart-integration component of the Printcart Web to Print Product Designer for WooCommerce plugin allows attackers to inject malicious SQL commands through unsanitized input. The vulnerability affects all versions through 2.4.0, potentially allowing unauthorized database access, data exfiltration, or manipulation.

MitigationImplement parameterized queries or prepared statements for all database interactions, and apply proper input validation and sanitization on all user-supplied parameters before including them in SQL queries. Users should monitor for vendor patches and update promptly.

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

CVSS breakdown

From the vector

Attack vector: Network
Complexity: Low
Privileges: Low
User interaction: None
Scope: Changed
Confidentiality: High
Integrity: None
Availability: Low

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

Am I affected?

dbcve checks

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

Verify Printcart plugin is installed

Check your WordPress installation for the Printcart Web to Print Product Designer plugin in wp-content/plugins/ directory or via WordPress admin plugin list

Affected if The Printcart plugin is found in the WordPress plugins directory or listed in the admin panel
Determine installed plugin version

Access WordPress admin > Plugins > Printcart Web to Print Product Designer, or open the main plugin PHP file and locate the version definition (typically in the plugin header or a version constant)

Affected if The installed version is 2.4.0 or any earlier version (all versions through 2.4.0 are affected)
Confirm printcart-integration component is active

Check if the printcart-integration functionality is enabled in the plugin settings, or review the plugin files for the printcart-integration module being loaded

Affected if The printcart-integration component is present and loaded by the plugin
Identify user-facing input points

Review plugin configuration for any frontend forms, API endpoints, or parameters that pass user input to the printcart-integration component

Affected if User-supplied input can be passed to the printcart-integration module without sanitization

You are affected if the Printcart Web to Print Product Designer for WooCommerce plugin version 2.4.0 or earlier is installed and the printcart-integration component is active in your WordPress environment.

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

Remediation

dbcve · scoped

Mitigation available No clean upgrade yet — mitigate in the meantime

Mitigation

Implement parameterized queries or prepared statements for all database interactions, and apply proper input validation and sanitization on all user-supplied parameters before including them in SQL queries. Users should monitor for vendor patches and update promptly.

Recommended fix Moderate confidence

Latest version available from WordPress plugin repository (version > 2.4.0)

Check the WordPress admin panel for the Printcart Web to Print Product Designer for WooCommerce plugin version
If the installed version is <= 2.4.0, update to the latest available version from the WordPress plugin repository or the vendor
After updating, verify the plugin functions correctly and test that the SQL injection vulnerability is resolved
Ensure WordPress, WooCommerce, and all other plugins are also kept up to date

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

Have this fixed Scoped from the published advisory

Consultation2.0 h
Implementation4.0 h
Testing3.0 h
Review / QA2.0 h

11.0 hours of engineering $1,930

Get help mitigating

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

Scan for this in your stack

Free · runs locally

dbcve dependency scanner

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

Primary sources

patchstack.com
nvd.nist.govNVD record

Practitioner notes

Contributed

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

Notes0 Guidelines

Know something about CVE-2025-24780?

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.

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

At a glance

A fix existsA vendor remedy is published

Severity 8.5 High

Exploit likelihood EPSS, next 30 days 0.3%

Remediation

A high-priority fix

Have this fixed 11 hrs · Moderate

Typical engagement from $1,930

Get a fix See the full breakdown ↓

A high-priority vulnerability. Send your environment and a specialist will scope CVE-2025-24780 and return a fixed quote and timeline.

You’ll deal with our team directly and deploy the reviewed fix to staging first — never straight to production.

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.

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.

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.

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.

Check your environment

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.

Scan for this in your stack

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

Practitioner notes

No notes yet

Official description

Technical summary

CVSS breakdown

Am I affected?

Remediation

References