CVE-2026-16968

GeoDirectory <= 2.8.167 - Information Exposure to Authenticated (Contributor+) User Email Disclosure

2026-07-27 00:00
Vaibhav Narkhede

Strategic Overview

Status
Patched in 2.8.168
Affected Version
<= 2.8.167
CVSS
4.3Medium
Weakness type
CWE-200 · Exposure of Sensitive Information to an Unauthorized Actor
CVE
CVE-2026-16968
View all GeoDirectory – WP Business Directory Plugin and Classified Listings Directory vulnerabilities

At a glance

CVE-2026-16968 is a medium-severity Exposure of Sensitive Information to an Unauthorized Actor vulnerability in the GeoDirectory WordPress plugin, affecting versions <= 2.8.167. It carries a CVSS score of 4.3 (reachable over the network; low attack complexity). Exploitation requires an authenticated account at Contributor level or above. The issue is fixed in version 2.8.168; sites on affected versions should update now. Disclosed July 2026, reported by Vaibhav Narkhede.

Vulnerability Overview

The GeoDirectory plugin for WordPress is vulnerable to Sensitive Information Exposure in versions up to, and including, 2.8.167. This is due to missing capability check before including user email addresses in the geodir_json_search_users AJAX response. This makes it possible for authenticated attackers, with contributor-level access and above, to obtain the email addresses of registered users by performing a user search query.

Technical Analysis

The vector marks this flaw as remotely reachable over the network, with low attack complexity — no special timing or configuration is needed, and no interaction from a victim user.

CWE-200: Exposure of Sensitive Information to an Unauthorized Actor

Reaching this weakness in GeoDirectory <= 2.8.167 takes an account at Contributor level or above. Sensitive information exposure means data the application intended to keep internal is returned to a caller who should not be able to see it.

The disclosed data — credentials, tokens, customer records or internal paths — is usually worth more as material for a follow-up attack than as an end in itself. For GeoDirectory the fix is 2.8.168: builds <= 2.8.167 are affected, anything from 2.8.168 onward is not.

Remediation

Update to version 2.8.168, or a newer patched version

How does WordSec protect against this?

The fix is the thing that ends this: GeoDirectory 2.8.168 closes this, and updating the plugin is the step that ends it.

  • Alerts

External References

Related records

Vulnerability data © Defiant, Inc., provided under the Wordfence Intelligence T&C