Cart Tracking For WoocommerceWordPress extension · Wpdever
CVE-2025-47538
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 wpdever Cart tracking for WooCommerce cart-tracking-for-woocommerce allows SQL Injection.This issue affects Cart tracking for WooCommerce: from n/a through <= 1.0.17.
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 · moderate confidenceSQL injection vulnerability in the cart-tracking-for-woocommerce WordPress plugin allows attackers to inject malicious SQL commands through unsanitized user input in the cart tracking functionality.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data
Cart Tracking For WoocommerceWordPress extension
<= 1.0.17CVSS 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
- High
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/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 checksWork through these to decide whether this CVE applies to you.
-
Identify if the plugin is installedCheck the WordPress plugins directory at wp-content/plugins/ for a folder named cart-tracking-for-woocommerce or Wpdever Cart Tracking For Woocommerce, or view installed plugins in WordPress admin under PluginsAffected if Plugin directory or entry exists in WordPress admin
-
Determine installed versionOpen the main plugin PHP file (usually cart-tracking-for-woocommerce.php) in the plugin folder and locate the Version header in the file comments, or view the version in WordPress admin Plugins pageAffected if Version number is 1.0.17 or lower
-
Confirm cart tracking feature is activeAccess the plugin settings in WordPress admin (typically under WooCommerce > Cart Tracking or a dedicated plugin settings page) and verify that cart tracking functionality is enabledAffected if Cart tracking feature is turned on in plugin settings
-
Audit for SQL injection exploitation attemptsReview web server access logs and WordPress debug logs for suspicious SQL syntax patterns (such as UNION SELECT, OR 1=1, -- comments) in requests targeting cart tracking endpoints or URLs containing tracking-related parametersAffected if Unusual SQL patterns found in logs related to cart tracking requests
Environment is affected if the cart-tracking-for-woocommerce plugin is installed with version 1.0.17 or lower and the cart tracking 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 dataUpgrade to a patched version of the plugin; if no patched version exists, implement prepared statements/parameterized queries and proper input validation on all database queries.
Fix this in Cart Tracking For Woocommerce
Scoped from the published advisory
- Consultation4.0 h
- Implementation6.0 h
- Testing4.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 $4,544.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-47538 — 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-47538 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