dbcve.org
Super Store FinderWordPress extension · Superstorefinder

CVE-2024-43978

CRITICAL · 9.8 CVSS v3.1 Published 2024-09-17
Fix available
A fix is available. Upgrade to 6.9.8 or later.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable No privileges 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 highwarden Super Store Finder superstorefinder-wp.This issue affects Super Store Finder: from n/a through < 6.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 confidence

SQL Injection vulnerability in the Super Store Finder WordPress plugin (superstorefinder-wp) allows attackers to inject malicious SQL commands via unsanitized input in the plugin's database queries. This critical flaw affects all versions prior to 6.9.8 and could allow unauthorized database access, data exfiltration, or privilege escalation.

MitigationUpgrade Super Store Finder plugin to version 6.9.8 or later to apply the vendor's input sanitization fix. If immediate patching is not possible, consider restricting access to the affected plugin endpoints via web application firewall rules.

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
Super Store FinderWordPress extension
Affected:< 6.9.8

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

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

  1. Locate the Super Store Finder plugin files
    Check your WordPress installation's wp-content/plugins/ directory for the superstorefinder-wp plugin folder
    Affected if The plugin folder exists in wp-content/plugins/
  2. Identify the installed version
    Open the main plugin PHP file (usually named superstorefinder-wp.php) and locate the version string in the plugin header comment, or check the readme.txt file for the Stable tag version
    Affected if The version found is lower than 6.9.8
  3. Verify the plugin is active
    Log into WordPress admin and navigate to Plugins > Installed Plugins to confirm the plugin status, or run WP-CLI command: wp plugin list --status=active --name='*superstorefinder*'
    Affected if The plugin is activated on the site
  4. Confirm vulnerability applicability
    Since this is a SQL injection via unsanitized database queries, the plugin must have its frontend or admin functionality accessible for an attacker to exploit the flawed queries - check if the plugin's public-facing features are in use
    Affected if The plugin is active and exposed via any frontend or admin endpoint

Your environment is affected if the Super Store Finder plugin is installed with a version lower than 6.9.8 and is currently active on the WordPress 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 6.9.8 or later
Fixed in 6.9.8
Interim mitigation

Upgrade Super Store Finder plugin to version 6.9.8 or later to apply the vendor's input sanitization fix. If immediate patching is not possible, consider restricting access to the affected plugin endpoints via web application firewall rules.

Recommended fix High confidence

Super Store Finder 6.9.8

  1. 1. Back up the WordPress site database and files before making any changes
  2. 2. Navigate to the WordPress admin dashboard > Plugins > Installed Plugins
  3. 3. Find 'Super Store Finder' in the plugin list
  4. 4. Click 'Update Now' if an update is available, or manually update to version 6.9.8
  5. 5. After updating, verify the plugin is running version 6.9.8 or later
  6. 6. Test the store locator functionality to ensure normal operation

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

Fix this in Super Store Finder Scoped from the published advisory
  • Consultation1.0 h
  • Implementation1.0 h
  • Testing2.0 h
  • Review / QA1.0 h
5.0 hours of engineering $860
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2024-43978 — 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-43978 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