CVE-2024-12416
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 · uneditedThe Live Sales Notification for Woocommerce – Woomotiv plugin for WordPress is vulnerable to SQL Injection via the 'woomotiv_seen_products_.*' cookie in all versions up to, and including, 3.6.1 due to insufficient escaping on the user supplied parameter and lack of sufficient preparation on the existing SQL query. This makes it possible for unauthenticated attackers to append additional SQL queries into already existing queries that can be used to extract sensitive information from the database.
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 confidenceThe Woomotiv WordPress plugin before version 3.6.2 is vulnerable to unauthenticated SQL injection via the 'woomotiv_seen_products_.*' cookie parameters. Attackers can inject malicious SQL queries through insufficiently escaped cookie values combined with unprepared SQL statements, enabling extraction of sensitive database information.
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
- Unchanged
- Confidentiality
- High
- Integrity
- None
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/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 checksWork through these to decide whether this CVE applies to you.
-
Verify Woomotiv plugin is installedAccess WordPress admin dashboard, navigate to Plugins > Installed Plugins, or inspect /wp-content/plugins/ directory for woomotiv folderAffected if Woomotiv plugin is present in the WordPress installation
-
Check installed Woomotiv versionView plugin details in WordPress admin or read the main plugin file header for 'Version' value, typically in woomotiv.phpAffected if Version is lower than 3.6.2 or version cannot be determined
-
Inspect cookie handling codeExamine plugin files for code handling 'woomotiv_seen_products_' prefixed cookies, look for $_COOKIE usage in PHP files within the plugin directoryAffected if Plugin code reads woomotiv_seen_products_* cookie values without sanitization
-
Verify SQL query executionReview plugin PHP files for SQL queries that use cookie values directly, look for $wpdb->prepare or similar prepared statement usageAffected if SQL queries incorporate cookie values without proper escaping or prepared statements
A WordPress site is affected if the Woomotiv plugin version is below 3.6.2 and the plugin processes the woomotiv_seen_products_* cookie parameters with direct SQL usage.
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.
dbcve · scopedUpdate the Woomotiv plugin to version 3.6.2 or later immediately. Review server access logs for signs of exploitation and consider database password rotation as a precautionary measure.
Latest version (greater than 3.6.1)
- Identify the 'Live Sales Notification for Woocommerce – Woomotiv' plugin in the WordPress plugin directory.
- Verify the installed version is 3.6.1 or lower (this is the last vulnerable version according to the description).
- Update the plugin to the latest version available in the WordPress plugin repository to receive the security fix.
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation2.0 h
- Testing1.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,744.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-12416 — 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-12416 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