CVE-2025-28898
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 SQL Injection.This issue affects WP Multistore Locator: from n/a through <= 2.5.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 confidenceSQL injection vulnerability in the WP Multistore Locator WordPress plugin allows attackers to inject malicious SQL commands via unsanitized input in certain plugin parameters. The vulnerability affects all versions up to and including 2.5.2.
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.
-
Locate WP Multistore Locator plugin filesAccess your WordPress installation via FTP or file manager. Navigate to /wp-content/plugins/ and check if a folder named 'wp-multistore-locator' or similar exists. Alternatively, log into WordPress admin and go to Plugins > Installed Plugins to find the plugin.Affected if The plugin folder 'wp-multistore-locator' is present in the plugins directory
-
Determine installed plugin versionIn WordPress admin, go to Plugins > Installed Plugins. Find WP Multistore Locator and note the version number displayed under the plugin name. Alternatively, open the main plugin PHP file (usually named like class-wp-multistore-locator.php or similar) and look for a Version constant in the plugin header comment.Affected if The displayed version is 2.5.2 or any lower version number (the vulnerability affects all versions up to and including 2.5.2)
-
Verify plugin is activeIn WordPress admin, go to Plugins > Installed Plugins. Check if WP Multistore Locator shows as 'Active' under the plugin status column.Affected if The plugin is currently activated; an inactive plugin still has the code present but the attack surface is reduced
-
Identify accessible plugin endpointsReview your web server access logs for requests to URLs containing the plugin slug (search for patterns like 'wp-multistore-locator', 'store-locator', or similar). Common vulnerable paths may include AJAX endpoints (/wp-admin/admin-ajax.php) or frontend ajax handlers exposed by the plugin.Affected if HTTP requests to plugin-related endpoints are being logged, indicating the plugin functionality is accessible to potential attackers
You are affected if WP Multistore Locator plugin is installed with version 2.5.2 or lower and the plugin is active, exposing potentially vulnerable parameters to user input.
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 the latest version of WP Multistore Locator when a patch is released. Until then, restrict access to the affected plugin endpoints and implement web application firewall rules to block SQL injection attempts.
- Consultation3.0 h
- Implementation6.0 h
- Testing3.0 h
- Review / QA3.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,272.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-28898 — 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-28898 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