CVE-2026-66680

CRITICALPre-NVD 9.39.3—
EchelonGraph scoreHIGH confidence

Score 9.3 from GitHub Security Advisory (severity: CRITICAL) published 2026-08-20. a secondary CVSS source baseline 9.3; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: ghsa, secondary
Trending — 3 sources updated this week
9.3EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: —CVSS: 9.3Exploit: None knownExposed: 0

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

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

CVSS v3
9.3
EG Score
9.3(high)
EG Risk
57(Track)
EG Risk 57/100SSVC: Track

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity93% × 45%
Exploitation0% × 40%
Automatability100% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
—
EPSS %ILE
—
KEV
Not listed

Published

August 20, 2026

Last Modified

August 20, 2026

Advisory Details (1)

Auto-updated Aug 20, 2026
No patch confirmed yet.
generic

undefined in undefined undefined undefined - Patchstack

https://patchstack.com/database/wordpress/plugin/locatoraid/vulnerability/wordpress-locatoraid-store-locator-plugin-3-9-72-sql-injection-vulnerability?_s_id=cve

Vendor Advisories for CVE-2026-66680(1)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 12× in last 7d / 12× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

  1. 2026-08-21 05:02 UTCGHSA enrichment
  2. 2026-08-21 00:51 UTCGHSA enrichment
  3. 2026-08-20 20:42 UTCGHSA enrichment
  4. 2026-08-20 16:32 UTCEG score recompute
  5. 2026-08-20 16:32 UTCGHSA enrichment
  6. 2026-08-20 16:07 UTCEG score recompute
  7. 2026-08-20 16:07 UTCGHSA enrichment
  8. 2026-08-20 12:49 UTCEG score recompute
  9. 2026-08-20 12:49 UTCGHSA enrichment
  10. 2026-08-20 12:19 UTCEG score recompute
  11. 2026-08-20 12:12 UTCEG score recompute
  12. 2026-08-20 12:11 UTCMITRE cvelistV5first tracked

Related CVEs(same CWE)

Frequently asked(4)

What is CVE-2026-66680?
CVE-2026-66680 is a critical vulnerability published on August 20, 2026. Unauthenticated SQL Injection in Locatoraid Store Locator <= 3.9.72 versions.
When was CVE-2026-66680 disclosed?
CVE-2026-66680 was first published in the National Vulnerability Database on August 20, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
What is the CVSS score of CVE-2026-66680?
CVE-2026-66680 has a CVSS v3 base score of 9.3 (NVD).
How do I remediate CVE-2026-66680?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-66680, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

Explore the affected products and dependency analysis for CVE-2026-66680

Explore →

Is Your Infrastructure Affected by CVE-2026-66680?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Start Free Scan →Browse All CVEs