CVE-2025-39445
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 highwarden Super Store Finder superstorefinder-wp allows SQL Injection.This issue affects Super Store Finder: from n/a through <= 7.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 · moderate confidenceA critical SQL injection vulnerability exists in the Super Store Finder WordPress plugin (versions <= 7.2) allowing unauthenticated attackers to inject malicious SQL commands via unsanitized input parameters in the plugin's store search or lookup functionality, potentially enabling full database compromise including extraction, modification, or deletion of data.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
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
- Changed
- Confidentiality
- High
- Integrity
- None
- Availability
- Low
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:N/A:L
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 Super Store Finder plugin is installedNavigate to WordPress admin dashboard > Plugins > Installed Plugins and look for 'Super Store Finder' in the listAffected if The plugin appears in the installed plugins list
-
Check installed plugin versionIn the Plugins list, click on 'Super Store Finder' details or hover over it to display the version number; compare against the affected version 7.2 and belowAffected if The installed version is 7.2 or any version number less than or equal to 7.2
-
Confirm store search functionality is accessibleVisit the storefront page where Super Store Finder search/locator is displayed (typically a store locator shortcode page); verify the search form accepts user input for location or store lookupAffected if The store search or store locator functionality is publicly accessible and functional on the website
-
Inspect HTTP requests for unsanitized parametersUse browser developer tools or a proxy to capture a store search request; examine the request parameters (such as search queries, location fields, or filter inputs) to see if they are passed directly to SQL queries without apparent sanitizationAffected if Input parameters in store search requests appear to be passed directly to database queries without visible escaping or prepared statements
A WordPress site is affected if the Super Store Finder plugin version 7.2 or lower is installed and the store search/locator functionality is enabled and accessible to users.
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 dataApply the vendor's security patch immediately upon release; in the interim, disable the plugin or implement a WAF rule to block SQL injection attack patterns while monitoring for exploitation attempts.
- Consultation4.0 h
- Implementation2.0 h
- Testing8.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,928.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-39445 — 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-2025-39445 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