← WordPress Vulnerabilities
WordPress security by component

Super Store Finder

Super Store Finder is a WordPress component with 5 published CVE records in this archive. The latest tracked vulnerability was published Feb 09, 2025; the highest CVE/CNA score is 9.3.

Plugin slug: super-store-finder

CVE-2024-13440: Super Store Finder: SQL injection

Super Store Finder is affected by SQL injection. The vulnerable path is reachable without authentication. A successful request can alter database queries and expose or modify WordPress data.

PublishedFeb 09, 2025
Safe version guidanceSee mitigation notes
Safe version
Feb 09, 2025 CVE-2024-13440
Super Store Finder: SQL injection
Super Store Finder is affected by SQL injection. The vulnerable path is reachable without authentication. A successful request can alter database queries and expose or modify WordPress data.
See mitigation notes
CVE8.2
NVD7.5
Sep 18, 2024 CVE-2024-43975
Super Store Finder: Cross-site scripting
Super Store Finder is affected by cross-site scripting. Exposure depends on how the affected operation is made reachable by the site. Injected script can execute in the affected site's origin when the vulnerable output is viewed.
See mitigation notes
CVE7.1
NVD6.1
Sep 17, 2024 CVE-2024-43978
Super Store Finder: SQL injection
Super Store Finder is affected by SQL injection. Exposure depends on how the affected operation is made reachable by the site. A successful request can alter database queries and expose or modify WordPress data.
See mitigation notes
CVE9.3
NVD9.8
Sep 17, 2024 CVE-2024-43976
Super Store Finder: SQL injection
Super Store Finder is affected by SQL injection. Exposure depends on how the affected operation is made reachable by the site. A successful request can alter database queries and expose or modify WordPress data.
See mitigation notes
CVE9.3
NVD9.8
Sep 19, 2023 CVE-2023-5054
Super Store Finder: A security weakness
Super Store Finder is affected by a security weakness. The vulnerable path is reachable without authentication. The resulting impact depends on how the affected component exposes the vulnerable operation.
See mitigation notes
CVE5.8
NVD5.3