ZeroHour

CVE-2026-84813

moderate

Unauthenticated SQL Injection in WordPress GeoDirectory Plugin

CVSS 3.1
9.3 critical
EPSS
<1%p15
Published
()
Modified
AI analysis

GeoDirectory versions up to and including 2.8.174 contain an unauthenticated SQL injection flaw (CWE-89) in which attacker-controlled input reaches a database query without proper sanitization. Because the flaw is reachable over the network without authentication or user interaction, an unauthenticated attacker can send crafted requests to trigger it. Successful exploitation primarily exposes database contents (high confidentiality impact, per the CVSS score), with only limited availability impact and no direct integrity impact; exposed data could include directory listings and other site data stored in the WordPress database. Any WordPress site running GeoDirectory 2.8.174 or earlier is affected. Exploitation has not been confirmed: there is no public proof-of-concept, the CVE is not in CISA KEV, and EPSS puts 30-day exploitation probability at only about 0.2%.

What to do: Update GeoDirectory to the latest release (any version newer than 2.8.174) as soon as possible, since no authentication is required for exploitation. Until patched, sites should check access logs for suspicious requests hitting directory/search parameters and consider applying a WAF rule that blocks common SQL injection patterns.

Affected
AyeCode GeoDirectory (WordPress plugin)<= 2.8.174
Estimated exposure
moderate≈10,000+ WordPress sites (wordpress.org active-install count) — The GeoDirectory plugin is listed on wordpress.org with roughly 10,000 or more active installations, so on the order of ten thousand sites run the plugin and are in scope until they update.

Order-of-magnitude estimate by the model from install counts, market share and public scan data it knows; verify before quoting.

Description

Unauthenticated SQL Injection in GeoDirectory <= 2.8.174 versions.

Ecosystems
WordPress
Weakness
CWE-89
Vector
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:N/A:L

In the news

No ingested article mentions this CVE yet.