dbcve.org
Super Store FinderWordPress extension · Superstorefinder

CVE-2024-43976

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

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 (versions <= 6.9.7) allows attackers to inject malicious SQL commands through unsanitized user input, potentially enabling unauthorized data access or database compromise.

MitigationUpdate to the latest version of Super Store Finder plugin when available; if no patch exists, disable the plugin until a fix can be implemented. The fix requires implementing parameterized queries or proper input sanitization on all database interactions.

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. Confirm Super Store Finder plugin is installed
    In WordPress admin dashboard, go to Plugins > Installed Plugins and look for 'Super Store Finder' in the list. Alternatively, check the /wp-content/plugins/superstorefinder directory exists.
    Affected if Plugin is not installed or not present on the system
  2. Check installed plugin version
    In WordPress admin, go to Plugins > Installed Plugins, find Super Store Finder, and view the version number under the plugin name. Or check the main plugin file (superstorefinder.php) for the 'Version' header comment.
    Affected if Version number is 6.9.7 or lower
  3. Compare version against affected range
    The affected versions are <= 6.9.7. If your installed version is less than 6.9.8, the vulnerability is present.
    Affected if Installed version is less than 6.9.8
  4. Review access logs for SQL injection indicators
    Examine web server access logs (Apache error.log, Nginx access.log) for requests to Super Store Finder endpoints containing SQL fragments like UNION SELECT, OR 1=1, or single quotes in parameters.
    Affected if Unusual SQL syntax appears in logged requests to plugin URLs

You are affected if the Super Store Finder plugin is installed with version 6.9.7 or lower, as this version range contains the unsanitized SQL injection vulnerability.

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

Update to the latest version of Super Store Finder plugin when available; if no patch exists, disable the plugin until a fix can be implemented. The fix requires implementing parameterized queries or proper input sanitization on all database interactions.

Recommended fix Moderate confidence

Super Store Finder version 6.9.8

  1. Log in to the WordPress admin dashboard
  2. Navigate to Plugins > Installed Plugins
  3. Find "Super Store Finder" in the plugin list
  4. If an update is available, click "Update Now" to upgrade to version 6.9.8
  5. Alternatively, manually download version 6.9.8 from the WordPress plugin repository or the vendor
  6. Deactivate the current plugin, delete the old version, then upload and install version 6.9.8
  7. After upgrade, verify the plugin is functioning correctly and test store locator functionality
  8. Consider running a SQL injection vulnerability scan to confirm remediation

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

Fix this in Super Store Finder Scoped from the published advisory
  • Consultation4.0 h
  • Implementation6.0 h
  • Testing4.0 h
  • Review / QA2.0 h
16.0 hours of engineering $2,840
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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