Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain
-
AccessLocate GeoDirectory single-item REST route
-
ExploitSupply ID of non-public listing
-
ImpactReceive title, permalink and card fields
Vulnerability Assessment
| Weakness |
CWE
OWASP Top 10:2025
A01:2025 - Broken Access Control
ASVS 5.0
V14 - Data Protection Data exposure prevention
MITRE ATT&CK
2 techniques across 2 tactics: Collection, Discovery The technique list with ATT&CK links and the kill-chain view is part of the Basic plan and up. |
| Exploitation Conditions | Exploitation requires a target site running the GeoDirectory plugin at a version before 2.8.194 that contains non-public listings (draft, pending, private or trashed) and that exposes the plugin's single-item map-popup REST route, which is standard plugin functionality rather than a non-default toggle. The attacker must supply or enumerate the numeric listing ID of a non-public listing. No authentication, privileges or user interaction are required (PR:N/UI:N), so the practical limiting factors are: the leak is confined to the title, permalink and card fields (not the full listing body or private owner data), and the attacker must know or guess valid listing IDs. Sites with no non-public listings have no data to disclose. |
| Impact | This is a genuine but moderate-priority information-disclosure issue, not a high-urgency emergency. The CVSS 3.1 base score is 5.3 (Medium) with vector AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N - remote, low-complexity, unauthenticated, with only a LOW confidentiality impact and no integrity or availability impact, consistent with the description's limited leak (title, permalink and card fields of non-public listings). The exploitation-probability signals reinforce a measured view rather than an alarmist one: EPSS is 0.20% at the 9th percentile (low), there is no CISA KEV listing (not confirmed actively exploited), and the exploit reference is a WPScan advisory that is a public PoC reference, not verified as working exploit code. The vuln.today decision label is 'this_month', which aligns with a scheduled-remediation posture rather than act_now/emergency. The signals are mutually consistent: easy to trigger (AV:N/AC:L/PR:N) but low concrete impact (C:L only, metadata of unpublished listings), so ease of access is offset by limited payoff. No key signals conflict here; the main residual uncertainty is that the CPE vendor is recorded as 'unknown' rather than the actual maintainer, which does not change the risk picture. |
| Exploit ScenarioDerived | An unauthenticated attacker enumerates numeric listing IDs and calls one of GeoDirectory's single-item map-popup REST routes for each ID, receiving the title, permalink and card fields of listings that are still in draft, pending, private or trashed status and should not be publicly visible. Because no authentication or user interaction is required (AV:N/PR:N/UI:N), this can be scripted at scale to harvest metadata about not-yet-published or withdrawn listings. A public PoC reference exists via WPScan; it is not verified as working exploit code. |
Get an e-mail when this CVE is exploited, patched or re-scored. Free account.
Alert meAnalysisAIv1 – Oct 24, 2026
Unauthenticated visitors to WordPress sites running GeoDirectory before 2.8.194 can retrieve the title, permalink and card fields of draft, pending, private and trashed listings through one of the plugin's single-item map-popup REST routes, which performs no status or ownership check on the supplied listing ID (CVSS 5.3, CWE-200). Exploitation is straightforward wherever that route is reachable and non-public listings exist, but disclosure is confined to those card-level fields rather than the full listing body or private owner data, and the attacker must know or guess a valid numeric listing ID. A vendor patch (2.8.194) is available, EPSS is 0.20% (9th percentile), there is no CISA KEV entry, and the referenced WPScan publication is a PoC reference that is not verified as working exploit code.
RemediationAI
Vendor-released patch: upgrade the GeoDirectory plugin to 2.8.194 or later, which is the fixed version listed in the WPScan advisory (https://wpscan.com/vulnerability/2901f8f3-0b35-4565-b248-6c0dfc5de894/) and reflected in the EUVD range 0 < 2.8.194. The available sources document updating as the remediation and do not describe separate vendor workarounds, so any interim measure is a compensating control rather than a supported fix: blocking or restricting the plugin's single-item map-popup REST route at the WAF or web-server layer stops the disclosure but breaks listing map popups on the site, and reducing the number of non-public listings or their predictability limits what can be enumerated while leaving the underlying missing check in place. Given the this_month priority, the low EPSS score (0.20%, 9th percentile) and the absence of KEV listing, upgrade during the normal patch cycle rather than as an emergency change.
Affected VersionsENISA
Affected Packages
Source: OSV (Open Source Vulnerabilities)
Affects your stack
Affects 1 package in euvd
Checking this CVE against your own stacks and servers is part of the Basic plan and up.
Technical ContextAI · show details
GeoDirectory is a WordPress directory plugin that stores each listing as a custom post type and renders listing information, including the map popup, via plugin REST endpoints. The flaw is a missing authorization/state check in the single-item route that builds a listing's map-popup payload: the handler accepts a caller-supplied listing ID and returns the title, permalink and card fields without verifying that the listing is published or that the requester owns it, which is CWE-200 exposure of sensitive information to an unauthorized actor. Because the CVSS vector is AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N, the issue is remotely reachable without credentials or user interaction and affects confidentiality only, at low impact. Listing IDs in WordPress are numeric post IDs that are often sequential, which makes enumeration plausible once a site is targeted; the practical constraints are that only the three card-level fields leak and that the route must be present, which is standard plugin functionality rather than a non-default option. The CPE string records the vendor as unknown, so version-based scanning should key on the plugin slug and the 2.8.194 fixed version rather than on a vendor name.
Know when Geodirectory gets its next vulnerability
- Watch products and get an email when something new is published
- Check this CVE against your own stack and servers
- Exploit and PoC references, threat intelligence from 22 sources
No credit card · 7-day full trial
Severity by source
AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N
Remote, low-complexity, unauthenticated REST request with no user interaction yields AV:N/AC:L/PR:N/UI:N; only limited metadata of non-public listings leaks, so C:L and I:N/A:N.
Primary rating from Vendor (WPScan).
CVSS VectorVendor: WPScan
Lifecycle Timeline
3DescriptionCVE.org
The GeoDirectory WordPress plugin before 2.8.194 does not perform any status or ownership check when rendering a listing's map-popup through one of its single-item REST routes, allowing unauthenticated users to read the title, permalink and card fields of non-public (draft, pending, private and trashed) listings by supplying the listing ID.
Threat Intelligence Overview
How this decision was reached
The engine reads each signal below and applies a fixed list of rules from top to bottom. The first rule that matches sets the recommended action – like a statement, every line is shown.
What every action level means
SSVC AssessmentENISA
Priority Score
Attack Technique
Information disclosure occurs when an application unintentionally exposes sensitive data that aids attackers in reconnaissance or directly compromises security.
More in Geodirectory
View allGeoDirectory, a WordPress directory plugin, writes administrator-supplied text into a generated PHP file inside its own
Stored cross-site scripting in the GeoDirectory WordPress plugin before 2.8.194 allows an authenticated user holding the
Information disclosure in the GeoDirectory WordPress plugin (before 2.8.168) exposes the email addresses of all register
Authenticated path traversal in the GeoDirectory WordPress plugin before 2.8.194 allows any user holding a Subscriber-le
The GeoDirectory WordPress plugin before 2.8.120 does not validate and escape some of its shortcode attributes before o
The GeoDirectory Business Directory WordPress plugin before 2.1.1.3 was vulnerable to Authenticated Stored Cross-Site Sc
Unauthenticated SQL injection in the GeoDirectory WordPress plugin (versions up to and including 2.8.152) allows remote
SQL injection in the GeoDirectory WordPress plugin (versions 2.8.174 and earlier) lets unauthenticated remote attackers
GeoDirectory WordPress plugin versions before 2.8.194 fail to enforce status, ownership and password checks in an unauth
Cross-Site Request Forgery in the GeoDirectory WordPress plugin (versions ≤ 2.8.176) enables remote unauthenticated atta
Missing Authorization vulnerability in AyeCode - WP Business Directory Plugins GeoDirectory allows Exploiting Incorrectl
Improper Neutralization of Special Elements used in an SQL Command ('SQL Injection') vulnerability in AyeCode Ltd GeoDir
EUVD-2026-109222
GHSA-jf56-6mwc-cfqj
NVD
CVE.org
EPSS
Vulnrichment
Exploit-DB