Greenshift Woocommerce AddonWordPress extension · Wpsoul
CVE-2024-43943
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 Wpsoul Greenshift Woocommerce Addon allows SQL Injection.This issue affects Greenshift Woocommerce Addon: from n/a before 1.9.8.
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 Greenshift Woocommerce Addon allows attackers to inject malicious SQL commands through unsanitized input, potentially enabling unauthorized database access, data exfiltration, or data manipulation.
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
Greenshift Woocommerce AddonWordPress extension
< 1.9.8CVSS 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
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:L/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 Greenshift Woocommerce Addon is installedNavigate to WordPress admin > Plugins, or inspect the plugin directory /wp-content/plugins/ for a folder containing 'greenshift' or 'greenshift-woocommerce'Affected if plugin folder exists in the WordPress plugins directory
-
Check installed plugin versionIn WordPress admin > Plugins, find the Greenshift Woocommerce Addon entry and note the version number displayed under the plugin name, or open the main plugin PHP file and locate the 'Version' header commentAffected if version field shows a number lower than 1.9.8
-
Confirm version is within affected rangeCompare the identified version number against the affected range: any version below 1.9.8 is vulnerableAffected if installed version is less than 1.9.8 (e.g., 1.9.7, 1.9.6, 1.0.0, etc.)
User is affected if the Greenshift Woocommerce Addon plugin is installed and its version is below 1.9.8
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 · scoped1.9.8
Update to version 1.9.8 or later which contains the patch for this SQL injection vulnerability. If immediate patching is not feasible, consider deploying a WAF rule or temporarily disabling the affected plugin.
Version 1.9.8 or later of Greenshift Woocommerce Addon plugin
- Create a complete backup of your WordPress site including database and files
- Navigate to WordPress Admin > Plugins > Installed Plugins
- Find 'Greenshift Woocommerce Addon' in the plugin list
- Click 'Update now' if an update is available, or manually upload version 1.9.8 or later
- After update completes, verify the plugin version shows 1.9.8 or higher
- Test critical WooCommerce workflows (product pages, cart, checkout) to confirm functionality
Generated from the published advisory — verify against the referenced sources before acting.
Fix this in Greenshift Woocommerce Addon
Scoped from the published advisory
- Consultation3.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,832.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-43943 — 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-43943 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