CVE-2026-66450
Unauthenticated Local File Inclusion in Geo Mashup (WordPress plugin) <=1.13.18
Is CVE-2026-66450 being exploited?
Not confirmed. CVE-2026-66450 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.34% probability of exploitation in the next 30 days.
How severe is CVE-2026-66450?
CVE-2026-66450 is rated High with a CVSS score of 8.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-66450?
Yes. A fix has been recorded for CVE-2026-66450. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.
What does CVE-2026-66450 affect?
CVE-2026-66450 affects Geo Mashup WordPress plugin <= 1.13.18. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.
What should I do about CVE-2026-66450?
Upgrade Geo Mashup to patched version (>1.13.18); if not possible, disable/remove plugin and apply WAF rules.
Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.
Unauthenticated LFI allows arbitrary local file read; can expose configs/credentials and enable RCE if chained.
Immediate action required
- affected<= 1.13.18
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.