Unrestricted File UploadWeakness · CWE-434

CVE-2025-47641

CRITICAL · 10.0 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
Unrestricted Upload of File with Dangerous Type vulnerability in printcart Printcart Web to Print Product Designer for WooCommerce printcart-integration allows Upload a Web Shell to a Web Server.This issue affects Printcart Web to Print Product Designer for WooCommerce: from n/a through <= 2.3.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 · high confidence

The printcart-integration plugin for WooCommerce contains an unrestricted file upload vulnerability allowing attackers to upload malicious web shells to the server, potentially achieving remote code execution and full site compromise.

MitigationUpdate to the latest patched version of Printcart Web to Print Product Designer for WooCommerce. Until patched, disable the plugin or remove the affected printcart-integration component, and implement web application firewall rules to block suspicious file uploads.

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
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/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. Identify if printcart-integration plugin is installed
    Navigate to WordPress admin > Plugins and look for 'Printcart Web to Print Product Designer for WooCommerce' or 'printcart-integration' in the installed plugins list
    Affected if The plugin appears in the installed plugins list and is active
  2. Check the installed plugin version
    In WordPress admin > Plugins, click on the plugin to view its details, or inspect the plugin header in wp-content/plugins/printcart-integration/printcart-integration.php for the Version: field
    Affected if The version number cannot be determined or is older than the current patched release
  3. Verify file upload endpoint exposure
    Check for publicly accessible upload endpoints in the printcart-integration plugin directory, typically in ajax handlers or API files that handle product designer uploads. Look for files containing 'upload' or 'save' in the filename within the plugin folder
    Affected if The plugin contains file upload functionality that is accessible without authentication or proper validation
  4. Inspect upload directories for suspicious files
    Check common upload folders such as wp-content/uploads/printcart/, wp-content/uploads/, and wp-content/plugins/printcart-integration/assets/ for newly created PHP files or files with double extensions (e.g., shell.php.jpg)
    Affected if Unexpected PHP files, web shells, or files with suspicious names are found in upload directories
  5. Review access logs for file upload patterns
    Examine web server access logs for POST requests to printcart-related endpoints that include file upload parameters, looking for requests to upload directories from unknown IP addresses
    Affected if Logs show file upload requests to printcart endpoints from unauthorized or external IP addresses

Your environment is affected if the printcart-integration plugin for WooCommerce is installed and active, particularly if the version is unknown or older than the patched release, and file upload functionality is accessible.

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 to the latest patched version of Printcart Web to Print Product Designer for WooCommerce. Until patched, disable the plugin or remove the affected printcart-integration component, and implement web application firewall rules to block suspicious file uploads.

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-47641 — 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 sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2025-47641 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