---
id: CVE-2026-15275
title: >-
  The WP Multi Store Locator Pro plugin for WordPress is vulnerable to generic
  SQL Injection via the 'store_locatore_search_radius' parameter in all versions
  up to, and including, 4.5.1 due to insufficient escaping on the user supplied
  par…
summary: >-
  The WP Multi Store Locator Pro plugin for WordPress is vulnerable to generic
  SQL Injection via the 'store_locatore_search_radius' parameter in all versions
  up to, and including, 4.5.1 due to insufficient escaping on the user supplied
  par…
severity: high
cvss: 7.5
cvssVector: 'CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N'
cwe:
  - CWE-89
vendor: wpexpertsio
product: WP Multi Store Locator Pro
affected:
  - wp_multi_store_locator_pro <= 4.5.1
published: '2026-09-18'
updated: '2026-09-19'
sourceUpdated: '2026-09-19T15:16:58.363'
source: NVD
sourceUrl: 'https://nvd.nist.gov/vuln/detail/CVE-2026-15275'
references:
  - url: 'https://codecanyon.net/item/wp-multi-store-locator-pro/19385351'
    label: security@wordfence.com
  - url: >-
      https://www.wordfence.com/threat-intel/vulnerabilities/id/d18fd2a8-a95c-40e2-bf35-333ee853639d?source=cve
    label: security@wordfence.com
tags:
  - nvd
  - cve.org
epss: 0.00374
epssPercentile: 0.28643
ssvc:
  exploitation: none
  automatable: 'yes'
  technicalImpact: partial
  timestamp: '2026-09-19T13:19:51.885186Z'
ingestedAt: '2026-09-18T08:38:04.100Z'
---

## Overview

The WP Multi Store Locator Pro plugin for WordPress is vulnerable to generic SQL Injection via the 'store_locatore_search_radius' parameter in all versions up to, and including, 4.5.1 due to insufficient escaping on the user supplied parameter and lack of sufficient preparation on the existing SQL query. This makes it possible for unauthenticated attackers to append additional SQL queries into already existing queries that can be used to extract sensitive information from the database. The injection occurs in a numeric, unquoted SQL context, meaning WordPress's wp_magic_quotes() addslashes-based protection cannot neutralize the payload, and the AJAX handler is registered on wp_ajax_nopriv_make_search_request with no nonce or capability check, making it fully accessible without authentication.

## Remediation

Refer to the linked advisories for vendor-supplied fixes and affected version ranges.
