The GeoDirectory WordPress plugin before 2.8.195 does not perform any status or ownership check when rendering a
Source GCVE Database
Not known to be exploited : upgrade to 2.8.195 soon.
Data as of 28 Oct 2026, 07:27 UTC
Rated High by Threat Radar's AI analysis · CVSS not yet scored by NVD
- Patch
- Available – fixed in 2.8.195
Exploitation evidence
Disclosed: evidence found.
CVE published 28 Oct 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: 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 26 Oct 2026.
What to do
Upgrade GeoDirectory (WordPress plugin) to 2.8.195.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| GeoDirectory | Affected
| Fixed in
|
AI-suggested
Upgrade the GeoDirectory WordPress plugin to version 2.8.195 or later where this issue is fixed. Since the vulnerability is resolved in 2.8.195, applying this official fix is the recommended remediation.
Description
A vulnerability in the GeoDirectory WordPress plugin before version 2.8.195 allows users with Contributor role and above to view content and custom fields of other users' draft, pending, private, and trashed listings. This occurs because the plugin does not perform status or ownership checks when rendering listings referenced by an id attribute in its field shortcodes.