CVE-2025-22639
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 · uneditedImproper Neutralization of Special Elements used in an SQL Command ('SQL Injection') vulnerability in Techspawn Distance Rate Shipping for WooCommerce distance-rate-shipping-for-woocommerce-pro allows Blind SQL Injection.This issue affects Distance Rate Shipping for WooCommerce: from n/a through <= 1.3.4.
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 confidenceA blind SQL injection vulnerability exists in the Techspawn Distance Rate Shipping for WooCommerce plugin (versions up to 1.3.4). Attackers can inject malicious SQL queries through unsanitized user input in the shipping rate calculation functionality, potentially allowing data exfiltration from the WordPress database.
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
- 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? 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 checksWork through these to decide whether this CVE applies to you.
-
Verify the plugin is installedLog in to WordPress admin and navigate to Plugins, or inspect the wp-content/plugins directory for a folder named 'distance-rate-shipping-for-woocommerce' or similar Techspawn shipping plugin folderAffected if The Techspawn Distance Rate Shipping plugin is found in the WordPress installation
-
Check the installed plugin versionIn WordPress admin, view the plugin details to see the version number, or open the plugin's main PHP file and look for the 'Version' header in the plugin commentsAffected if The installed version is 1.3.4 or any lower version (the vulnerability affects versions up to 1.3.4)
-
Confirm the shipping rate calculation feature is activeNavigate to WooCommerce > Settings > Shipping and check if any Techspawn Distance Rate Shipping zones or methods are enabled and configured with rate calculationsAffected if The shipping calculation functionality is enabled and configured with at least one shipping zone or rate
-
Inspect for signs of SQL injection exploitationReview WordPress debug logs (wp-content/debug.log if enabled), server access logs, and database query logs for suspicious SQL syntax, unusual WHERE clauses, or unexpected time delays that could indicate blind SQL injection testingAffected if Unusual SQL patterns are found in logs, or unexpected data access has occurred from the WordPress database user
You are affected if the Techspawn Distance Rate Shipping for WooCommerce plugin is installed with version 1.3.4 or lower and the shipping rate calculation feature is enabled.
Generated from the published advisory. Verify against your own configuration.
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 dataUpdate to a patched version of the plugin immediately. If no patch is available, disable the plugin and migrate to an alternative shipping solution.
- Consultation2.0 h
- Implementation2.0 h
- Testing3.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,512.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-22639 — 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 sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2025-22639 in production — separate from our analysis above.
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.
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.
- 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