Super Store FinderWordPress extension · Superstorefinder
CVE-2024-43975
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 Input During Web Page Generation ('Cross-site Scripting') 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 · moderate confidenceA Cross-site Scripting (XSS) vulnerability in the Super Store Finder WordPress plugin (versions up to 6.9.7) allows attackers to inject malicious JavaScript code through unsanitized user input that gets rendered in web pages. This improper neutralization of input during page generation enables stored XSS attacks against site administrators or visitors.
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
<= 6.9.7CVSS 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
- Required
- Scope
- Changed
- Confidentiality
- Low
- Integrity
- Low
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/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.
-
Confirm Super Store Finder plugin is installedIn WordPress admin, navigate to Plugins > Installed Plugins and look for 'Super Store Finder' or 'Superstorefinder Super Store Finder' in the list of installed pluginsAffected if Plugin is present in the plugins directory
-
Identify the installed plugin versionIn WordPress admin, go to Plugins > Installed Plugins, find Super Store Finder, and note the version number displayed beneath the plugin nameAffected if Version number is 6.9.7 or lower
-
Compare version against vulnerable rangeCompare the installed version to the affected range: versions 6.9.7 and below are vulnerableAffected if Installed version is less than or equal to 6.9.7
-
Verify the plugin is activeIn WordPress admin > Plugins, confirm the Super Store Finder plugin shows as 'Active' (not deactivated or deleted)Affected if Plugin is currently active on the WordPress site
-
Identify user input points in the pluginNavigate to the plugin settings or store locator admin pages and locate any fields that accept user-supplied data such as store names, addresses, or custom labels that get rendered on the frontendAffected if The plugin accepts and stores user input that could be rendered without sanitization
A WordPress site is affected if it has Super Store Finder plugin installed, active, and running version 6.9.7 or lower, with the plugin accepting and displaying user-supplied data on web pages.
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.
From vendor dataUpdate Super Store Finder to the latest patched version. If immediate update is unavailable, implement output encoding and input validation on all user-supplied data before rendering, and consider deploying a WAF rule to block XSS attack patterns.
Fix this in Super Store Finder
Scoped from the published advisory
- Consultation2.0 h
- Implementation4.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 $3,088.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-43975 — 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-43975 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