CVE-2026-104899
Unauthenticated LFI in GeoDirectory WordPress plugin enabling PHP inclusion and potential RCE.
Is CVE-2026-104899 being exploited?
Not confirmed. CVE-2026-104899 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.64% probability of exploitation in the next 30 days.
How severe is CVE-2026-104899?
CVE-2026-104899 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-104899?
Yes. A fix has been recorded for CVE-2026-104899. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.
What does CVE-2026-104899 affect?
CVE-2026-104899 affects GeoDirectory WordPress plugin ≤ 2.8.187, Any WordPress site with the GeoDirectory plugin installed. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.
What should I do about CVE-2026-104899?
Update GeoDirectory to the patched release immediately; disable/remove plugin if unable to patch.
Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.
Unauthenticated LFI via 'design_type' and trivial nonce allows inclusion/execution of attacker-supplied .php files → remote code execution, data theft, auth bypass.
Patch when possible
- affected<= 2.8.187
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.