CVE-2026-15300
SQL injection in GEO my WP plugin via URL coords (distance, lat, lng).
Is CVE-2026-15300 being exploited?
Not confirmed. CVE-2026-15300 does not appear in CISA's Known Exploited Vulnerabilities catalog, which records only exploitation that has been observed and reported publicly. That is evidence of absence of a report, not evidence the flaw is unattacked. EPSS currently estimates a 0.62% probability of exploitation in the next 30 days.
How severe is CVE-2026-15300?
CVE-2026-15300 is rated Critical with a CVSS score of 9.1. Severity describes how bad exploitation would be, not how likely it is: pair it with exploitation evidence before deciding what to patch first.
Is there a patch for CVE-2026-15300?
Yes. A fix has been recorded for CVE-2026-15300. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.
What does CVE-2026-15300 affect?
CVE-2026-15300 affects GEO my WP plugin <= 4.5.4, WordPress sites using GEO my WP. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.
What should I do about CVE-2026-15300?
Update GEO my WP to 4.5.5+; apply WAF rules to block non-numeric coord payloads.
Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.
SQL injection via URL params enabling data exfiltration, DB modification, or time-based DoS (e.g., SLEEP payloads).
Immediate action required
- affected<= 4.5.4
As published in the CVE Program record. A version outside these ranges is not a statement that it is unaffected — vendors sometimes understate a range, and distribution-backported builds carry upstream numbers that do not reflect what was patched into them.