Live Exposure Defense: From CVE to Confirmed Exposure in 12 Hours – See more

New CVE Detected

CVE-2026-66680 – Unauthenticated SQL Injection – Locatoraid Store Locator WordPress Plugin (≤ 3.9.72

Be the first to know when new zero-days emerge:

Summary

CVE-2026-66680 is an unauthenticated SQL injection vulnerability affecting the Locatoraid Store Locator plugin for WordPress, developed by Plainware. The flaw allows attackers to inject malicious SQL through the plugin without any authentication, and has been assigned a CVSS v3.1 base score of 9.3 (Critical). It affects all plugin versions up to and including 3.9.72.

Technical details

  • Root cause: Improper neutralization of special elements used in SQL commands (CWE-89) within the Locatoraid Store Locator plugin, allowing untrusted input to be incorporated into SQL queries.
  • Trigger conditions: No authentication or user interaction is required to exploit the flaw; it can be triggered via crafted requests to the vulnerable plugin functionality (blind SQL injection).
  • Attack vector: Network — the vulnerability is remotely exploitable over HTTP(S) against internet-facing WordPress sites running the plugin.
  • Impact: High confidentiality impact (unauthorized reading of database contents, e.g., credentials, user data) and low availability impact; integrity impact is not affected. The CVSS vector indicates a scope change, meaning the impact can extend beyond the vulnerable component itself.

Affected software

  • Locatoraid Store Locator WordPress plugin, versions up to and including 3.9.72.

Severity

  • CVSS v3.1 Base Score: 9.3 (Critical)
  • Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:N/A:L

Mitigation and recommended actions

  • Immediate: Upgrade Locatoraid Store Locator to a version newer than 3.9.72, which resolves this vulnerability.
  • If patching is not immediately possible: Restrict or monitor access to the plugin’s public-facing endpoints, deploy a Web Application Firewall (WAF) rule to detect and block SQL injection patterns, and review database and web server logs for signs of exploitation attempts.

How IONIX identifies potentially affected assets

IONIX matches the following signal against data already collected when it crawled the asset; identifying the technology sends no request beyond that crawl.

  • Raw response body: /wp-content/plugins/locatoraid/

References

Are you exposed?

Get a free report of your organization’s exposure to this CVE and threat

How IONIX’s External Exposure Management Platform Detects and Validates
Zero-Days to Shrink MTTR

1

Map your entire attack surface (continously)

IONIX uses multi-factor discovery methods, including DNS analysis, certificate mapping, metadata inspection, and more, to automatically map every internet-facing asset across your environment. This includes cloud instances, third-party platforms, shadow IT, and even forgotten infrastructure that traditional tools miss.

2

Monitor for new CVEs

Dozens of threat intel feeds using agentic technology are continuously analyzed to detect the appearance of proof-of-concept code, exploit kits, and indicators of active targeting. IONIX goes further by applying AI to proactively evaluate whether emerging vulnerabilities are likely to be exploited, even before PoCs go public.

3

Identify Potential External Exposures

Not all CVEs matter. IONIX filters vulnerabilities by asking attacker-centric questions: Can it be reached from the internet? Does it require authentication? Is it being exploited in the wild? This dramatically reduces noise and focuses teams on threats that can actually be weaponized.

4

Create Safe, Scalable Exploit Validations

IONIX transforms real-world PoCs into safe, non-intrusive test payloads that can be run in production environments without disruption. These simulations are precisely targeted to the systems that are vulnerable, ensuring rapid validation without unnecessary load.

5

Execute Exploit Validations

By combining context about software stack, versioning, exposure status, and reachability, IONIX ensures that only the right payloads are executed against the right assets, maximizing efficiency and minimizing risk.

6

Drive Fast and Actionable Remediation

Results are routed through integrations with ticketing, SOAR, and SIEM tools. Issues are written in plain language, bundled into remediation clusters, and prioritized based on asset criticality, exploitability, and blast radius. This shortens mean time to remediation (MTTR) and empowers teams to act with confidence.

Are you exposed?

Get a free report of your organization’s exposure to this CVE and threat

Subscribe to Threat Center RSS

Copy/paste the link below into your preferred RSS reader or follow these instructions to subscribe to Slack alerts.

Get Real-Time CVE Alerts to Your Email

Be the first to know when new zero-days emerge