dbcve.org
SQL InjectionWeakness · CWE-89

CVE-2025-32128

HIGH · 7.6 CVSS v3.1 Published 2025-04-10
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
82/100
Remediation priority · High
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 aaronfrey Nearby Locations nearby-locations allows SQL Injection.This issue affects Nearby Locations: from n/a through <= 1.1.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 confidence

SQL injection vulnerability in the Nearby Locations WordPress plugin allows remote attackers to inject malicious SQL commands through unsanitized input parameters in the nearby-locations component. The lack of proper input validation and use of string concatenation for SQL queries enables attackers to manipulate database queries.

MitigationUpgrade to a patched version of Nearby Locations plugin that implements prepared statements/parameterized queries, or if no patch is available, manually refactor all SQL queries to use parameterized queries with proper input sanitization.

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 checks

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

  1. Identify if Nearby Locations plugin is installed
    Navigate to WordPress admin dashboard under Plugins > Installed Plugins and look for 'Nearby Locations' in the list, or check the filesystem at wp-content/plugins/ for a directory named 'nearby-locations' or similar
    Affected if The Nearby Locations plugin appears in the installed plugins list
  2. Determine the installed plugin version
    In the WordPress Plugins admin page, click on the plugin name to view details and find the version number, or open the main plugin PHP file (usually nearby-locations.php or similar) and check the plugin header comment for 'Version: x.x.x'
    Affected if The version shown cannot be confirmed as a patched version that uses prepared statements
  3. Verify the nearby-locations component is active
    Check if the plugin is activated in WordPress admin (Plugin status shows 'Active') and if there is a frontend feature or endpoint related to nearby-locations (such as an AJAX handler, shortcode, or page that displays location data)
    Affected if The plugin is active and the nearby-locations functionality is accessible to users or visitors
  4. Inspect SQL query handling in plugin code
    Using a file editor or grep, search within the plugin directory for SQL query patterns that use string concatenation with user input (look for '$wpdb->prepare' with direct variable insertion, or $wpdb->query/->get_results with concatenated strings containing $_POST, $_GET, or $_REQUEST variables)
    Affected if The plugin code contains SQL queries built by concatenating user-supplied input without using parameterized queries or proper escaping

A user is affected if the Nearby Locations plugin is installed, active, and its code contains unsanitized SQL queries that concatenate user input from the nearby-locations component.

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

Upgrade to a patched version of Nearby Locations plugin that implements prepared statements/parameterized queries, or if no patch is available, manually refactor all SQL queries to use parameterized queries with proper input sanitization.

Recommended fix Moderate confidence

Version 1.1.2 or later (latest available version)

  1. 1. Log in to the WordPress admin dashboard
  2. 2. Navigate to Plugins > Installed Plugins
  3. 3. Locate the 'Nearby Locations' plugin by aaronfrey
  4. 4. If an update is available, click 'Update Now' to update to the latest version
  5. 5. After updating, verify the plugin is functioning correctly on the site
  6. 6. Consider taking a backup of the site before performing the update

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

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing2.0 h
  • Review / QA1.0 h
9.0 hours of engineering $1,600
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,560.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-32128 — 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-32128 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