CVE-2025-49328
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 Agile Logix Store Locator WordPress agile-store-locator allows SQL Injection.This issue affects Store Locator WordPress: from n/a through <= 1.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 · moderate confidenceSQL injection vulnerability in the Agile Store Locator WordPress plugin allows attackers to inject malicious SQL commands through unsanitized user input, potentially enabling unauthorized database access, data exfiltration, or manipulation of store locator 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
- High
- User interaction
- None
- Scope
- Changed
- Confidentiality
- High
- Integrity
- None
- Availability
- Low
CVSS:3.1/AV:N/AC:L/PR:H/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 Agile Store Locator plugin is installedLog into the WordPress admin dashboard and navigate to Plugins > Installed Plugins. Look for 'Agile Store Locator' in the list of active plugins.Affected if The plugin appears in the installed plugins list, indicating the plugin is present in the environment
-
Identify the installed plugin versionIn the WordPress admin under Plugins > Installed Plugins, click on 'Agile Store Locator' to view the plugin details, or check the plugin header in the main plugin file to read the Version field.Affected if The version number displayed is 1.5.1 or lower, placing it within the vulnerable version range
-
Determine if the store locator search functionality is publicly accessibleVisit the page where the store locator shortcode or widget is deployed (typically any page using [asl_store_locator] or similar shortcode). Attempt to access the store search feature to confirm it accepts user input.Affected if The store locator search interface is live and accepts user-provided search parameters, which could be exploited for SQL injection
-
Review web server or application logs for suspicious SQL patternsExamine access logs for the site hosting the plugin, searching for unusual SQL keywords (UNION, SELECT, INSERT, DROP) in URL parameters, especially those related to store search queries.Affected if Log entries show SQL injection attempt patterns targeting store locator parameters, indicating active exploitation attempts
If the Agile Store Locator plugin is installed with version 1.5.1 or lower and the store search feature is accessible, the environment is affected by this 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 agile-store-locator plugin to the latest version beyond 1.5.1 that contains the security fix; until patched, consider deploying a WAF rule to block SQL injection attack patterns.
- Consultation3.0 h
- Implementation2.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 $2,832.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-49328 — 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-49328 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