dbcve.org
Server-Side Request Forgery (SSRF)Weakness · CWE-918

CVE-2025-12375

MEDIUM · 6.4 CVSS v3.1 Published 2026-02-19
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
70/100
Remediation priority · Elevated
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
The Printful Integration for WooCommerce plugin for WordPress is vulnerable to Server-Side Request Forgery in all versions up to, and including, 2.2.11 via the advanced size chart REST API endpoint. This is due to insufficient validation of user-supplied URLs before passing them to the download_url() function. This makes it possible for authenticated attackers, with Contributor-level access and above, to make web requests to arbitrary locations originating from the web application which can be used to query and modify information from internal services.

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 Printful Integration for WooCommerce plugin lacks proper URL validation on its advanced size chart REST API endpoint. An authenticated attacker with Contributor-level access can supply arbitrary URLs that get processed by download_url(), enabling Server-Side Request Forgery to probe internal services and exfiltrate data.

MitigationUpdate the plugin to version 2.2.12 or later which includes proper URL validation. If immediate update is not possible, restrict Contributor-level REST API access or disable the advanced size chart feature until the patch can be applied.

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

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

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 plugin installation and version
    Navigate to WordPress admin > Plugins and locate 'Printful Integration for WooCommerce', or inspect the plugin file (usually at wp-content/plugins/printful-integration-for-woocommerce/printful-integration-for-woocommerce.php) to read the Version header
    Affected if Installed version is below 2.2.12
  2. Verify advanced size chart feature is enabled
    Check the plugin settings page in WordPress admin under WooCommerce > Printful settings, or look for any custom post type or database entry related to size charts (often stored as a custom post type or wp_options entry)
    Affected if The advanced size chart functionality is active in the environment
  3. Confirm Contributor role has REST API access
    In WordPress admin under Users > Roles, verify that the Contributor role retains the 'edit_posts' capability which grants access to the REST API by default, or attempt a test API call using a Contributor-level account to the endpoint /wp-json/printful/v1/size-chart/
    Affected if Contributor users can successfully make authenticated REST API requests (this is the default WordPress behavior)
  4. Inspect the size chart endpoint for URL handling
    Examine the plugin source code, specifically looking for the REST API route handler that processes the advanced size chart data (typically in includes/class-printful-rest-api.php or similar), and locate any call to download_url() function with user-supplied URL parameter
    Affected if The endpoint accepts and processes arbitrary URLs from the 'url' or similar parameter without validation

Environment is affected if the Printful Integration for WooCommerce plugin version is below 2.2.12, the advanced size chart feature is enabled, and Contributor-level users have REST API access, allowing them to inject arbitrary URLs through the size chart endpoint.

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
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Update the plugin to version 2.2.12 or later which includes proper URL validation. If immediate update is not possible, restrict Contributor-level REST API access or disable the advanced size chart feature until the patch can be applied.

Recommended fix High confidence

2.2.12

  1. 1. Log in to the WordPress admin dashboard
  2. 2. Navigate to Plugins > Installed Plugins
  3. 3. Locate the 'Printful Integration for WooCommerce' plugin
  4. 4. If an update is available, click 'Update Now' to upgrade to version 2.2.12 or higher
  5. 5. Alternatively, manually download version 2.2.12 from the WordPress plugin repository and upload via Plugins > Add New > Upload Plugin
  6. 6. Verify the updated version number reflects 2.2.12 or later after updating

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

Have this fixed Scoped from the published advisory
  • Consultation3.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA2.0 h
12.0 hours of engineering $2,130
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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