Skip to main content

GeoDirectory EUVDEUVD-2026-111727

| CVE-2026-113494 LOW
Information Exposure (CWE-200)
2026-10-28 contact@wpscan.com GHSA-4562-6r2h-7rvw
2.7
CVSS 3.1 · Vendor: wpscan
View

Attack ChainAIDerived

Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain

  1. Access
    Obtain Contributor-level account
  2. Exploit
    Insert field shortcode with target listing id
  3. Execution
    Render page bypassing status/ownership check
  4. Impact
    Disclose other users' private listing content and custom 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

Requires an authenticated WordPress account with the Contributor role or higher on a site running GeoDirectory before 2.8.195, and the attacker must reference a victim listing by its id attribute within a GeoDirectory field shortcode. Exposure is limited to the content and custom fields of listings in non-public states (draft, pending, private, trashed); it does not permit modification or deletion. The principal limiting factor is the Contributor-level authentication requirement, which rules out unauthenticated access, and the impact is confined to information disclosure of listing data rather than site compromise.

Impact

This is a low-severity information-disclosure issue (CWE-200) and the signals are mutually consistent rather than conflicting. The vendor CVSS vector (AV:N/AC:L/PR:H/UI:N/S:U/C:L/I:N/A:N = 2.7) shows network-reachable but authenticated exploitation with only limited confidentiality impact and no integrity or availability impact. EPSS is 0.16% (5th percentile), there is no CISA KEV listing, and the vuln.today Decision label is 'monitor' - all pointing to low real-world urgency. The one internal tension worth flagging: the vendor scored PR:H, yet the description states exploitation only requires the Contributor role 'and above,' which is a low-privilege authenticated WordPress role - PR:L is the more defensible choice, which would raise the base score to roughly 4.3. Either way this remains a bounded data-exposure bug affecting only non-public listing content, not a code-execution or takeover primitive. Net assessment: a genuine but low-priority vulnerability - patch in normal cycles, not an emergency.

Exploit ScenarioDerived

An attacker who holds (or registers for) a Contributor-level account on a GeoDirectory-powered WordPress site creates or edits content containing a GeoDirectory field shortcode that references another user's listing by its id attribute. Because the plugin performs no status or ownership check, the rendered output leaks the content and custom fields of that listing even when it is in draft, pending, private, or trashed state. No public exploit is identified in the provided data, and the trigger beyond supplying the id attribute is not detailed in the available sources.

Monitor Track and reassess. Why: LOW severity (CVSS 0.1-3.9).
Patch available 0.2% exploitation probability (EPSS)

Get an e-mail when this CVE is exploited, patched or re-scored. Free account.

Alert me

AnalysisAIv1 – Oct 28, 2026

The GeoDirectory WordPress plugin before 2.8.195 renders listing data through its field shortcodes without verifying the status or ownership of the referenced listing, so an authenticated user holding the Contributor role or higher can read the content and custom fields of other users' draft, pending, private and trashed listings by supplying the corresponding id attribute. The exposure is read-only - no modification or deletion is possible - and is gated by the requirement for a Contributor-level account on the target site. A vendor patch is available in 2.8.195, EPSS is low at 0.16% (5th percentile) and there is no public exploit or KEV entry identified at time of analysis.

RemediationAI

Vendor-released patch: update GeoDirectory to version 2.8.195 or later - the vendor confirms a fix is available and the WPScan advisory (https://wpscan.com/vulnerability/29efa17c-fee7-4bd5-b52c-d0ce73bd786c/) documents the vulnerable range as everything below 2.8.195. Because exploitation requires a Contributor-or-above account, an interim exposure reduction is to audit and temporarily reduce the number of users holding Contributor or higher on sites where GeoDirectory cannot be updated immediately; the trade-off is that this blocks legitimate authoring and submission workflows for those accounts until the plugin is patched. Updating to 2.8.195 is the documented complete fix; no other vendor-documented workaround is listed in the available sources.

Affected VersionsENISA

GeoDirectory 0 <2.8.195

Affected Packages

euvd geodirectory fix: 2.8.195

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

This is a CWE-200 information-exposure defect in a WordPress plugin's shortcode rendering path. GeoDirectory field shortcodes accept an id attribute that selects which listing to render, and the handler fails to compare the requested listing's post status (draft, pending, private, trashed versus publish) or its author against the requesting user before emitting content and custom field values. WordPress shortcodes execute wherever content is rendered, so any Contributor-or-above account able to author content containing such a shortcode can use it as a read primitive against listing IDs. The weakness class is a missing authorization/state check (exposure of sensitive information to an actor not explicitly authorized), not a memory-safety or injection issue; the description does not state whether the leak occurs on preview, on the front end, or in both, so the exact rendering context is unconfirmed. No CPE identifiers were supplied in the source data; the EUVD affected range is recorded as "GeoDirectory 0 <2.8.195".

Know when WordPress 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

Vendor (wpscan) PRIMARY 2.7 LOW
AV:N/AC:L/PR:H/UI:N/S:U/C:L/I:N/A:N
vuln.today AI 4.3 MEDIUM

Contributor is a low-privilege authenticated role so PR:L (not PR:H); low confidentiality impact from leaked listing fields, with no integrity or availability impact.

3.1 AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:N
4.0 AV:N/AC:L/AT:N/PR:L/UI:N/VC:L/VI:N/VA:N/SC:N/SI:N/SA:N

Primary rating from Vendor (wpscan).

CVSS VectorVendor: wpscan

Attack Vector
Network
Attack Complexity
Low
Privileges Required
High
User Interaction
None
Scope
Unchanged
Confidentiality
Low
Integrity
None
Availability
None

Lifecycle Timeline

3
CVSS changed
Oct 28, 2026 - 18:22 NVD
2.7 (LOW)
Patch available
Oct 28, 2026 - 07:16 EUVD
CVE Published
Oct 28, 2026 - 06:16 cve.org
UNKNOWN (no severity yet)

DescriptionCVE.org

The GeoDirectory WordPress plugin before 2.8.195 does not perform any status or ownership check when rendering a listing referenced by an id attribute in its field shortcodes, allowing users with the Contributor role and above to disclose the content and custom fields of other users' draft, pending, private and trashed listings.

Threat Intelligence Overview

EPSS Score
0.2%
Top 95% exploitable
Prevalence
Medium
popular WordPress directory-listing plugin, common but not universally deployed
Data Quality
4 sources
Confidence: Medium

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.

SignalValue
Severity LOW
CISA KEV No
Public POC No
EPSS 0.2%
Patch available Yes
Active threat No
Deciding rule
LOW severity (CVSS 0.1-3.9)
What every action level means
Emergency Immediate action required. Criteria: CRITICAL + in CISA KEV (actively exploited) without patch, OR CRITICAL + EPSS > 30% without patch, OR CRITICAL + active threat signals without patch.
Act Now Prioritize within 24-48h. Criteria: in KEV with patch available, OR CRITICAL + public POC, OR HIGH + EPSS > 10%, OR CRITICAL + active threat, OR any CRITICAL severity.
This Week Schedule remediation this week. Criteria: HIGH severity (CVSS 7.0-8.9). Patch within normal change window.
This Month Plan within 30 days. Criteria: MEDIUM severity (CVSS 4.0-6.9), lower exploitation probability. Include in regular patch cycle.
Monitor Track and reassess. Criteria: LOW severity (CVSS 0.1-3.9), minimal exploitation risk. No immediate action needed.

SSVC AssessmentENISA

SSVC Decision· derived
Defer
Exploitation· derived
None
System Exposure· derived
Open
Automatable· derived
No
Human Impact· derived
Low

Priority Score

14
Low Medium High Critical
KEV: 0
EPSS: 0
CVSS: +14
PoC: 0
Weaponized: 0
Threat intel: 0
Gov advisory: 0

Attack Technique

Information disclosure occurs when an application unintentionally exposes sensitive data that aids attackers in reconnaissance or directly compromises security.

CVE-2016-10033 CRITICAL POC
9.8 Dec 30

The mailSend function in the isMail transport in PHPMailer before 5.2.18 might allow remote attackers to pass extra para

CVE-2016-10045 CRITICAL POC
9.8 Dec 30

The isMail transport in PHPMailer before 5.2.20 might allow remote attackers to pass extra parameters to the mail comman

CVE-2023-6553 CRITICAL POC
9.8 Dec 15

The Backup Migration plugin for WordPress is vulnerable to Remote Code Execution in all versions up to, and including, 1

CVE-2024-5084 CRITICAL POC
9.8 May 23

The Hash Form - Drag & Drop Form Builder plugin for WordPress is vulnerable to arbitrary file uploads due to missing fil

CVE-2024-44000 CRITICAL POC
9.8 Oct 20

Authentication bypass in the LiteSpeed Cache WordPress plugin (versions prior to 6.5.0.1) allows unauthenticated remote

CVE-2024-8353 CRITICAL POC
9.8 Sep 28

The GiveWP - Donation Plugin and Fundraising Platform plugin for WordPress is vulnerable to PHP Object Injection in all

CVE-2020-36847 CRITICAL POC
9.8 Jul 12

The Simple File List plugin for WordPress through version 4.2.2 contains an unauthenticated remote code execution vulner

CVE-2025-11749 CRITICAL POC
9.8 Nov 05

The AI Engine WordPress plugin through version 3.1.3 exposes Bearer Token values through the /mcp/v1/ REST API endpoint

CVE-2025-27007 CRITICAL POC
9.8 May 01

The SureTriggers WordPress plugin through version 1.0.82 contains a privilege escalation vulnerability that allows unaut

CVE-2016-1209 CRITICAL POC
9.8 May 14

The Ninja Forms plugin before 2.9.42.1 for WordPress allows remote attackers to conduct PHP object injection attacks via

CVE-2024-4443 CRITICAL POC
9.8 May 22

The Business Directory Plugin - Easy Listing Directories for WordPress plugin for WordPress is vulnerable to time-based

CVE-2026-63030 CRITICAL POC
9.8 Jul 17

Remote code execution in WordPress 6.9.x (before 6.9.5) and 7.0.x (before 7.0.2) arises from a REST API batch endpoint r

This site uses cookies essential for authentication and security. No tracking or analytics cookies are used. Privacy Policy