CVE-2026-15300

CRITICALPre-NVD 9.19.1—
EchelonGraph scoreHIGH confidence

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

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, secondary
Trending — 4 sources updated this week
9.1
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS: 0%CVSS: 9.1Exploit: NoneExposed: 0

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

The GEO my WP plugin for WordPress was vulnerable to SQL Injection via the 'distance', 'lat', and 'lng' parameters in versions up to, and including, 4.5.4. The values were read from $_SERVER['QUERY_STRING'] via parse_str() (bypassing wp_magic_quotes, which does not cover $_SERVER), then passed through bare esc_sql() before being interpolated into unquoted numeric positions in the proximity-search query (HAVING/SELECT clause distance math, BETWEEN bounding-box pre-filter) built by gmw_locations_query() in plugins/posts-locator/includes/class-gmw-wp-query.php. Because esc_sql() only escapes string delimiters and these positions are numeric, payloads such as 1 OR SLEEP(3) survived sanitization. Fixed in 4.5.5 by adding an upstream is_numeric() guard that short-circuits the WHERE clause to AND 1 = 0 when either coordinate is non-numeric, and by replacing the three esc_sql() calls with (float) casts.

CVSS v3
9.1
EG Score
9.1(high)
EPSS
27.1%
KEV
Not listed

Published

July 10, 2026

Last Modified

July 10, 2026

References (6)

Vendor Advisories for CVE-2026-15300(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 72× in last 7d / 72× 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-07-15 23:11 UTCEG score recompute
  2. 2026-07-15 23:11 UTCGHSA enrichment
  3. 2026-07-15 18:53 UTCEG score recompute
  4. 2026-07-15 18:53 UTCGHSA enrichment
  5. 2026-07-15 16:57 UTCEPSS rescore
  6. 2026-07-15 14:34 UTCEG score recompute
  7. 2026-07-15 14:34 UTCGHSA enrichment
  8. 2026-07-15 10:16 UTCEG score recompute
  9. 2026-07-15 10:16 UTCGHSA enrichment
  10. 2026-07-15 05:58 UTCEG score recompute
  11. 2026-07-15 05:58 UTCGHSA enrichment
  12. 2026-07-15 02:00 UTCEPSS rescore
  13. 2026-07-15 01:28 UTCEG score recompute
  14. 2026-07-15 01:28 UTCGHSA enrichment
  15. 2026-07-14 21:10 UTCEG score recompute
  16. 2026-07-14 21:10 UTCGHSA enrichment
  17. 2026-07-14 16:52 UTCEG score recompute
  18. 2026-07-14 16:52 UTCGHSA enrichment
  19. 2026-07-14 12:34 UTCEG score recompute
  20. 2026-07-14 12:34 UTCGHSA enrichment
  21. 2026-07-14 08:16 UTCEG score recompute
  22. 2026-07-14 08:16 UTCGHSA enrichment
  23. 2026-07-14 03:57 UTCEG score recompute
  24. 2026-07-14 03:57 UTCGHSA enrichment
  25. 2026-07-13 23:39 UTCEG score recompute
Show 47 more
  1. 2026-07-13 23:39 UTCGHSA enrichment
  2. 2026-07-13 22:30 UTCEPSS rescore
  3. 2026-07-13 19:21 UTCEG score recompute
  4. 2026-07-13 19:21 UTCGHSA enrichment
  5. 2026-07-13 15:03 UTCEG score recompute
  6. 2026-07-13 15:03 UTCGHSA enrichment
  7. 2026-07-13 10:43 UTCEG score recompute
  8. 2026-07-13 10:43 UTCGHSA enrichment
  9. 2026-07-13 06:25 UTCEG score recompute
  10. 2026-07-13 06:25 UTCGHSA enrichment
  11. 2026-07-13 06:12 UTCEPSS rescore
  12. 2026-07-13 02:07 UTCEG score recompute
  13. 2026-07-13 02:07 UTCGHSA enrichment
  14. 2026-07-12 21:49 UTCEG score recompute
  15. 2026-07-12 21:49 UTCGHSA enrichment
  16. 2026-07-12 17:30 UTCEG score recompute
  17. 2026-07-12 17:30 UTCGHSA enrichment
  18. 2026-07-12 13:12 UTCEG score recompute
  19. 2026-07-12 13:11 UTCGHSA enrichment
  20. 2026-07-12 08:53 UTCEG score recompute
  21. 2026-07-12 08:53 UTCGHSA enrichment
  22. 2026-07-12 05:46 UTCEPSS rescore
  23. 2026-07-12 04:35 UTCEG score recompute
  24. 2026-07-12 04:35 UTCGHSA enrichment
  25. 2026-07-12 00:16 UTCEG score recompute
  26. 2026-07-12 00:16 UTCGHSA enrichment
  27. 2026-07-11 19:58 UTCEG score recompute
  28. 2026-07-11 19:58 UTCGHSA enrichment
  29. 2026-07-11 15:40 UTCEG score recompute
  30. 2026-07-11 15:40 UTCGHSA enrichment
  31. 2026-07-11 11:22 UTCEG score recompute
  32. 2026-07-11 11:22 UTCGHSA enrichment
  33. 2026-07-11 08:27 UTCEPSS rescore
  34. 2026-07-11 07:04 UTCEG score recompute
  35. 2026-07-11 07:04 UTCGHSA enrichment
  36. 2026-07-11 02:46 UTCEG score recompute
  37. 2026-07-11 02:46 UTCGHSA enrichment
  38. 2026-07-10 22:28 UTCEG score recompute
  39. 2026-07-10 22:28 UTCGHSA enrichment
  40. 2026-07-10 18:10 UTCEG score recompute
  41. 2026-07-10 18:10 UTCGHSA enrichment
  42. 2026-07-10 13:51 UTCEG score recompute
  43. 2026-07-10 13:51 UTCGHSA enrichment
  44. 2026-07-10 09:33 UTCEG score recompute
  45. 2026-07-10 09:33 UTCGHSA enrichment
  46. 2026-07-10 05:15 UTCEG score recompute
  47. 2026-07-10 05:13 UTCMITRE cvelistV5first tracked

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2026-15300?
CVE-2026-15300 is a critical vulnerability published on July 10, 2026. The GEO my WP plugin for WordPress was vulnerable to SQL Injection via the 'distance', 'lat', and 'lng' parameters in versions up to, and including, 4.5.4. The values were read from $SERVER['QUERYSTRING'] via parsestr() (bypassing wpmagicquotes, which does not cover $SERVER), then passed through…
When was CVE-2026-15300 disclosed?
CVE-2026-15300 was first published in the National Vulnerability Database on July 10, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-15300 actively exploited?
CVE-2026-15300 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 27.1% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
What is the CVSS score of CVE-2026-15300?
CVE-2026-15300 has a CVSS v3 base score of 9.1 (NVD).
How do I remediate CVE-2026-15300?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-15300, 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-15300

Explore →

Is Your Infrastructure Affected by CVE-2026-15300?

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

Start Free Scan →Browse All CVEs