LiveActive security incident?Get immediate response
CVE Record

CVE-2026-66680: WordPress Locatoraid Store Locator plugin <= 3.9.72 - SQL Injection vulnerability

Unauthenticated SQL Injection in Locatoraid Store Locator <= 3.9.72 versions.

CriticalCVSS 9.3Not KEV-listedUpdated
Glexia's TakeAutomated analysiscritical

Security readout for executives and security teams

Plain-English summary

Locatoraid Store Locator for WordPress reportedly contains a critical SQL injection flaw affecting versions through 3.9.72. An unauthenticated internet user may manipulate database queries, potentially exposing sensitive database information and causing limited service disruption. The supplied sources do not document active exploitation or identify a confirmed fixed version.

Executive priority

Treat as an immediate inventory and remediation priority for internet-facing WordPress sites. The potential for unauthenticated database exposure drives urgency, although active exploitation is not documented. Require owners to confirm affected installations, follow authoritative remediation guidance, and temporarily disable unnecessary instances when a confirmed fix cannot be established.

Technical view

CVE-2026-66680 is classified as CWE-89: SQL injection. Its CVSS 3.1 score is 9.3, with network access, low complexity, no privileges, and no user interaction required. The vector indicates high confidentiality impact, low availability impact, no integrity impact, and changed scope. Public technical details remain limited.

Likely exposure

Internet-accessible WordPress sites running Locatoraid Store Locator 3.9.72 or earlier are the likely exposure group. Confirm installed versions directly. The structured affected record is internally inconsistent, listing “n/a” and default status “unaffected,” while the title and description explicitly state versions through 3.9.72 are vulnerable.

Exploitation context

No active exploitation is established by the supplied evidence, and the CVE is not identified as being in KEV. Nevertheless, unauthenticated network reachability, low attack complexity, and critical severity make exposed installations attractive targets. Treat suspicious database or plugin requests as requiring investigation, without assuming compromise solely from version presence.

Researcher notes

The primary claim is unauthenticated SQL injection in Locatoraid Store Locator through 3.9.72. No vulnerable parameter, endpoint, proof of concept, observed campaign, or fixed version appears in the supplied material. The affected-product structure conflicts with the narrative version range, so vulnerability managers should validate scope against updated authoritative records and vendor guidance.

Mitigation direction

  • Identify all WordPress sites using Locatoraid Store Locator and record their installed versions.
  • Check current vendor and Patchstack guidance for a confirmed fixed release or official mitigation.
  • Apply the confirmed remediation promptly after testing it in a representative environment.
  • Disable or remove the plugin where remediation cannot be confirmed and business operations permit.
  • Restrict unnecessary public access while remediation is pending.

Validation and detection

  • Verify the plugin version on every production, staging, and externally reachable WordPress instance.
  • Confirm remediation against current vendor or Patchstack guidance; the supplied bundle names no fixed version.
  • Review web, application, and database logs for anomalous requests involving the plugin.
  • Confirm disabled or removed copies are not still reachable through alternate sites or environments.
  • Retest normal locator functionality and monitor availability after remediation.
Prepared
Confidence
medium
Sources
3

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

cwe · medium confidence lookup

CWE-89: Database access and collection lookup

Injection into data stores can inform collection, data access, and exfiltration detection reviews. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.

Open ATT&CK lookup
description · low confidence lookup

Database behavior lookup

The CVE wording references database injection or access, so collection and exfiltration review may help. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.

Open ATT&CK lookup
cve · low confidence lookup

CVE-2026-66680 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
Critical
CVSS
9.3 (3.1)
Known Exploited
No
Published

Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:N/A:L

Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

1CVSS vectors
3Timeline events
1ADP providers
2Source links

SSVC decision data

CISA-ADPCISA Coordinator
Timestamp
Version
2.0.3
Exploitation: noneAutomatable: yesTechnical Impact: partial

CVSS vector scores

1 official score

We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.

ScoreVersionSeverityVectorExploitImpactSource
9.3CVSS 3.1CriticalCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:N/A:L3.94.7Patchstack

Vulnerability scoring details

Base CVSS 3.1 score

9.3Critical
CVSS 3.1 vector shape for CVE-2026-66680Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:N/A:L

Attack Vector
NetworkAdjacentLocalPhysical
Attack Complexity
LowHigh
Privileges Required
NoneLowHigh
User Interaction
NoneRequired
Scope
ChangedUnchanged
Confidentiality Impact
HighLowNone
Integrity Impact
HighLowNone
Availability Impact
HighLowNone

Vulnerability timeline

Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.

  1. CVE reservedCVE Program

    The CVE ID was reserved by the assigning CNA.

  2. CVE publishedCVE Program

    The CVE record was published.

  3. CVE updatedCVE Program

    The CVE record metadata indicates this as the latest update time.

ADP provider summaries

CISA-ADPCISA ADP Vulnrichment
other:ssvc
Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
plainwareLocatoraid Store Locatorlocatoraid, n/aunaffected
Weakness

CWE details

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.