dbcve.org
SQL InjectionWeakness · CWE-89

CVE-2025-67516

HIGH · 8.5 CVSS v3.1 Published 2025-12-09
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
91/100
Remediation priority · Urgent
Remotely reachable Zero-click

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 · unedited
Improper Neutralization of Special Elements used in an SQL Command ('SQL Injection') vulnerability in Agile Logix Store Locator WordPress agile-store-locator allows Blind SQL Injection.This issue affects Store Locator WordPress: from n/a through <= 1.6.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 · high confidence

The Agile Store Locator WordPress plugin (agile-store-locator) versions 1.6.2 and below contains a blind SQL injection vulnerability. Attackers can inject malicious SQL commands through unsanitized input parameters in the plugin, potentially allowing unauthorized database access, data exfiltration, or manipulation.

MitigationApply the latest plugin update when available; if no patch exists, disable the plugin immediately. Otherwise, implement parameterized queries or input validation/sanitization on all user-supplied parameters reaching database queries.

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
Low
User interaction
None
Scope
Changed
Confidentiality
High
Integrity
None
Availability
Low

CVSS:3.1/AV:N/AC:L/PR:L/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 checks

Work through these to decide whether this CVE applies to you.

  1. Check installed plugin version
    In WordPress admin, go to Plugins > Installed Plugins and find 'Agile Store Locator'. The version is displayed below the plugin name. Alternatively, check the plugin's main PHP file (wp-content/plugins/agile-store-locator/agile-store-locator.php) for the 'Version' header in the plugin comment block.
    Affected if The displayed version is 1.6.2 or any version lower (e.g., 1.6.1, 1.6.0, 1.5.x, etc.)
  2. Verify plugin is active
    In WordPress admin, go to Plugins > Installed Plugins and confirm the 'Agile Store Locator' plugin has the 'Activate' button (meaning it is currently running). Check the site front-end to confirm the store locator functionality is accessible.
    Affected if The plugin is active and the store locator feature is publicly accessible on the website
  3. Identify exposed plugin endpoints
    Check the site's public pages for any store locator functionality (search forms, map displays, store listings). Use browser developer tools or a site scanner to identify URLs that include 'agile-store-locator' or 'asl_' in the request parameters.
    Affected if The plugin's front-end search or lookup features are publicly reachable without authentication
  4. Audit database query parameters
    If you have access to the plugin source code, review PHP files in wp-content/plugins/agile-store-locator/ for direct use of $_GET, $_POST, or $_REQUEST variables in SQL queries without prepare() statements or sanitization functions.
    Affected if Code review reveals unsanitized input being used in database queries (this confirms the vulnerability is exploitable in the current installation)

You are affected if the Agile Store Locator plugin is installed at version 1.6.2 or lower AND is actively running with publicly accessible store locator features.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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.

dbcve · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Apply the latest plugin update when available; if no patch exists, disable the plugin immediately. Otherwise, implement parameterized queries or input validation/sanitization on all user-supplied parameters reaching database queries.

Recommended fix High confidence

Version 1.6.3 or later

  1. 1. Backup your WordPress site and database before making any changes
  2. 2. Navigate to Plugins > Installed Plugins in the WordPress admin dashboard
  3. 3. Locate the 'Agile Store Locator' plugin
  4. 4. Check if the current version is 1.6.2 or lower (vulnerable)
  5. 5. If vulnerable, click 'Update Now' to upgrade to version 1.6.3 or later
  6. 6. Alternatively, download the latest version from the WordPress plugin repository and upload via Plugins > Add New > Upload Plugin
  7. 7. Verify the update was successful by confirming the new version number
  8. 8. Test the store locator functionality to ensure the plugin still works correctly after the update

Generated from the published advisory — verify against the referenced sources before acting.

Have this fixed Scoped from the published advisory
  • Consultation3.0 h
  • Implementation2.0 h
  • Testing3.0 h
  • Review / QA2.0 h
10.0 hours of engineering $1,770
Get help mitigating

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 locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-67516 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2025-67516 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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