dbcve.org
Greenshift Query AddonWordPress extension · Wpsoul

CVE-2024-43942

HIGH · 8.8 CVSS v3.1 Published 2024-08-29
Fix available
A fix is available. Upgrade to 3.9.2 or later.
See remediation →
94/100
Remediation priority · Urgent
Remotely reachable Zero-click

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 · unedited
Improper Neutralization of Special Elements used in an SQL Command ('SQL Injection') vulnerability in Wpsoul Greenshift Query and Meta Addon allows SQL Injection.This issue affects Greenshift Query and Meta Addon: from n/a before 3.9.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 confidence

SQL injection vulnerability in Greenshift Query and Meta Addon WordPress plugin allows attackers to inject malicious SQL commands through unsanitized user inputs. This occurs due to improper neutralization of special elements in SQL queries, potentially allowing unauthorized database access, data exfiltration, or manipulation.

MitigationUpdate Greenshift Query and Meta Addon to version 3.9.2 or later to obtain the patched code. Until patched, consider disabling the affected plugin or deploying a WAF to filter SQL injection attack patterns.

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 Query AddonWordPress extension
Affected:< 3.9.2

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
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 checks

Work through these to decide whether this CVE applies to you.

  1. Verify Greenshift Query Addon is installed
    Navigate to WordPress admin dashboard > Plugins > Installed Plugins and look for 'Greenshift Query and Meta Addon' or 'Greenshift Query Addon' in the plugin list
    Affected if The plugin is present in the WordPress installation
  2. Identify the installed plugin version
    In the Plugins list, locate the Greenshift plugin and note the version number displayed beneath the plugin name, or check the plugin's main PHP file for the 'Version' header in the plugin comment block
    Affected if The displayed version number is lower than 3.9.2
  3. Confirm the vulnerability is exploitable
    Determine if the Query Addon functionality is actively enabled on the site - check if any custom queries, meta queries, or dynamic content blocks using the plugin are in use via the WordPress block editor or theme customizer
    Affected if The plugin is active and its query/meta features are being used on pages or posts
  4. Review server access logs for SQL injection patterns
    Inspect web server access logs (Apache/Nginx) for requests to wp-admin/admin-ajax.php or frontend endpoints containing suspicious SQL syntax (such as UNION SELECT, OR 1=1, or common SQL keywords in parameter values) directed at plugin endpoints
    Affected if Malformed SQL patterns are found in request parameters targeting plugin functionality

You are affected if the Greenshift Query Addon plugin is installed with a version lower than 3.9.2 and the query/meta features are actively in use on the site.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 · scoped
Upgrade available Upgrade to 3.9.2 or later
Fixed in 3.9.2
Interim mitigation

Update Greenshift Query and Meta Addon to version 3.9.2 or later to obtain the patched code. Until patched, consider disabling the affected plugin or deploying a WAF to filter SQL injection attack patterns.

Recommended fix High confidence

3.9.2

  1. 1. Create a full backup of the WordPress site including database and files.
  2. 2. Navigate to Plugins > Installed Plugins in the WordPress admin dashboard.
  3. 3. Locate the Greenshift Query Addon (Greenshift Query and Meta Addon) plugin.
  4. 4. Click Update Now to update the plugin to version 3.9.2, or manually upload version 3.9.2 if automatic update is not available.
  5. 5. Verify the plugin is running version 3.9.2 by checking the installed version number.
  6. 6. Test critical functionality to ensure the plugin continues to work correctly after the update.
  7. 7. Clear any caching systems (server-side cache, CDN cache, and browser cache) to ensure the patched code is served.

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Greenshift Query Addon Scoped from the published advisory
  • Consultation2.0 h
  • Implementation3.0 h
  • Testing2.0 h
  • Review / QA1.0 h
8.0 hours of engineering $1,420
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,272.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2024-43942 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2024-43942 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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