CVE-2026-114270: GeoDirectory (WordPress plugin) · Information Exposure
Affects GeoDirectory (WordPress plugin)Source CVE Database V5
Not known to be exploited : upgrade to 2.8.197 soon.
Data as of 29 Oct 2026, 07:26 UTC
Rated High by Threat Radar's AI analysis · CVSS not yet scored by NVD
Thin evidence
One scorer or none- Patch
- Available – fixed in 2.8.197
Exploitation evidence
Disclosed: evidence found.
CVE published 29 Oct 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 29 Oct 2026.
What to do
Upgrade GeoDirectory (WordPress plugin) to 2.8.197.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| GeoDirectory | Affected
| Fixed in
|
AI-suggested
Upgrade GeoDirectory to version 2.8.197 or later, where this vulnerability is fixed. Applying this official fix will restore proper enforcement of post password protection on listings.
Description
GeoDirectory WordPress plugin versions prior to 2.8.197 do not enforce post password protection on listings, allowing unauthenticated users to access content and custom fields of password-protected published listings.