CVE-2025-26974
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 WPExperts.io WP Multistore Locator wp-multi-store-locator allows Blind SQL Injection.This issue affects WP Multistore Locator: from n/a through <= 2.5.1.
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 confidenceA blind SQL injection vulnerability exists in the WP Multistore Locator WordPress plugin (versions 2.5.1 and below). Attackers can inject malicious SQL commands through unsanitized user input, potentially allowing unauthorized database access, data exfiltration, or manipulation.
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.
-
Confirm WP Multistore Locator plugin is installedLog in to WordPress admin dashboard and navigate to Plugins > Installed Plugins. Look for 'WP Multistore Locator' in the list of active plugins. Alternatively, check for the plugin directory at /wp-content/plugins/wpsl/ on the server file system.Affected if The plugin appears in the list of installed plugins or the wpsl directory exists on the server.
-
Identify installed plugin versionIn WordPress admin, click on the plugin name from the Plugins list to view its details, which typically displays the version number. If not accessible via admin, open the main plugin file (usually /wp-content/plugins/wpsl/wpsl.php) and locate the version comment in the file header.Affected if The displayed version number is 2.5.1 or lower.
-
Verify vulnerable version rangeCompare the identified version against the affected range. The vulnerability affects versions 2.5.1 and below, meaning any version from the plugin's initial release up to and including version 2.5.1 is vulnerable.Affected if The installed version is 2.5.1 or any earlier version number.
-
Identify SQL input pointsReview the plugin settings and any public-facing forms (such as store locator search forms) where users can submit input. The vulnerability exists in unsanitized user input that gets passed to SQL queries. Check plugin files in /wp-content/plugins/wpsl/includes/ for direct SQL query construction using user-supplied parameters.Affected if The plugin has active front-end forms or search functionality that accepts user input and the plugin code uses that input directly in database queries without prepared statements or escaping.
If WP Multistore Locator is installed and the version is 2.5.1 or below, the environment is affected by this blind SQL injection vulnerability.
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 the WP Multistore Locator plugin to the latest version immediately. If no patched version is available, disable the plugin until a fix is released.
- Consultation3.0 h
- Implementation6.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,984.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-26974 — 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-26974 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