Ti Woocommerce WishlistWordPress extension · Templateinvaders
CVE-2024-43917
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 TemplateInvaders TI WooCommerce Wishlist allows SQL Injection.This issue affects TI WooCommerce Wishlist: from n/a through 2.8.2.
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 confidenceSQL Injection vulnerability in TI WooCommerce Wishlist plugin allows attackers to inject malicious SQL queries through unsanitized input. The vulnerability exists in versions up to 2.8.2 and is rated critical due to the potential for full database compromise, including exfiltration of sensitive customer data or complete site takeover.
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
Ti Woocommerce WishlistWordPress extension
<= 2.8.2CVSS 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
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/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.
-
Verify TI WooCommerce Wishlist plugin is installedNavigate to WordPress admin > Plugins and locate 'TI WooCommerce Wishlist' by Templateinvaders in the installed plugins listAffected if The plugin appears in the plugins list
-
Check installed version numberIn the Plugins page, click on the plugin details or view the plugin version displayed next to its name. Alternatively, check the plugin's main PHP file header in wp-content/plugins/ti-woocommerce-wishlist/Affected if The displayed version is 2.8.2 or any version lower (e.g., 2.8.1, 2.7.0, etc.)
-
Confirm plugin is activeIn WordPress admin > Plugins, verify the TI WooCommerce Wishlist plugin shows as 'Active' rather than deactivatedAffected if Plugin is active and the version is 2.8.2 or below
-
Review web server access logs for SQL injection patternsExamine your web server access logs (typically in /var/log/apache2/ or /var/log/nginx/) for requests to your site containing SQL syntax in query parameters, such as single quotes, UNION SELECT, or common SQL injection keywordsAffected if Suspicious SQL syntax found in HTTP requests to wishlist functionality
-
Check database for unauthorized changesQuery your WordPress database tables (particularly wp_options, wp_users, and any custom wishlist tables) for unexpected entries, new admin users, or modified permissionsAffected if Unknown admin accounts or unexpected data in wishlist-related tables
You are affected if TI WooCommerce Wishlist plugin is installed, active, and running version 2.8.2 or lower.
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 TI WooCommerce Wishlist to the latest version once available, or implement input validation/parameterized queries at the application boundary as a compensating control until the vendor patch is released.
Fix this in Ti Woocommerce Wishlist
Scoped from the published advisory
- Consultation3.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,224.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-43917 — 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-2024-43917 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