CVE-2025-52720
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.5.
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 confidenceSQL Injection vulnerability in the Super Store Finder WordPress plugin (versions up to 7.5) allows attackers to inject malicious SQL commands via improper neutralization of special elements in SQL queries. The critical severity (CVSS 9.3) indicates unauthenticated attackers can potentially extract, modify, or delete database contents.
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 installedCheck for the plugin directory at wp-content/plugins/super-store-finder/ or list installed plugins via WordPress admin (Plugins > Installed Plugins) or WP-CLI: wp plugin list --name='super-store-finder'Affected if The plugin directory exists in the WordPress plugins folder, indicating the plugin is present
-
Determine installed plugin versionOpen the main plugin file (super-store-finder.php) and locate the 'Version' header in the plugin comment block, or check in WordPress admin plugin listAffected if Version number is 7.5 or lower (the vulnerability affects versions up to 7.5)
-
Confirm plugin is activeCheck WordPress admin > Plugins > Installed Plugins to verify Super Store Finder status shows 'Active', or run: wp plugin status super-store-finderAffected if Plugin is currently activated; inactive plugins cannot be exploited
-
Identify plugin endpoints handling user inputReview plugin source files in wp-content/plugins/super-store-finder/ for PHP files processing request parameters (GET/POST) used in SQL queries, such as search, filter, or AJAX handlersAffected if Plugin processes user-supplied input in database queries without proper parameterization; the specific vulnerable parameter varies by implementation
User is affected if Super Store Finder plugin versions 7.5 or below are installed AND active, and the plugin processes user input in SQL queries without prepared statements
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 to a patched version of Super Store Finder if available; otherwise, implement parameterized queries/prepared statements for all database interactions and validate/sanitize all user inputs before using them in SQL queries.
- Consultation4.0 h
- Implementation8.0 h
- Testing4.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 $5,120.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-52720 — 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-52720 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