Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain
-
AccessAuthenticate as Subscriber or above
-
DeliverySubmit front-end listing with crafted image URL
-
ExploitPlugin resolves URL to local path outside web root
-
ExecutionFile re-published at public URL, original deleted
-
ImpactDisclose sensitive file and destroy server data
Vulnerability Assessment
| Weakness |
CWE
OWASP Top 10:2025
A01:2025 - Broken Access Control
ASVS 5.0
V5 - File Handling Path canonicalization, traversal prevention
MITRE ATT&CK
2 techniques across 2 tactics: Discovery, Collection 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 account at Subscriber level or above on a WordPress site running GeoDirectory before 2.8.194 (PR:L), so either open user registration or an otherwise-obtained low-privilege account is a prerequisite. The attacker must use the plugin's front-end listing save feature and supply an image URL that the plugin consumes as a local filesystem path without validation. Exploitation is constrained to files whose names carry an allowed media extension, which limits which targets can be read or deleted; no victim interaction is needed (UI:N). The compromise is twofold: the targeted file is re-published at a public URL (disclosure) and its original is deleted (destruction) as a direct side effect of the same operation. |
| Impact | This is a medium-severity, authenticated path traversal (CWE-22) in the GeoDirectory WordPress plugin, and the signals are internally consistent rather than conflicting. The CVSS 3.1 vector (AV:N/AC:L/PR:L/UI:N/S:C/C:L/I:L/A:N, base 6.4) describes a network-reachable, low-complexity flaw that nonetheless requires authentication - PR:L maps to the Subscriber-level account the description names, so this is not a pre-auth mass-exploitation candidate. EPSS is low (0.20%, 10th percentile), the CVE is NOT listed in CISA KEV, and the exploit signal is only a WPScan reference that is not verified as working exploit code, so there is no evidence of active exploitation - this is a real but moderate priority, matching the vuln.today 'this_month' decision label rather than an emergency. The scope change (S:C) and dual read/delete impact raise its importance above a trivial info leak: an attacker can both exfiltrate files from outside the web root and destroy files, which is why the limited C:L/I:L still aggregates to 6.4. Net: a genuine issue to patch on a normal cycle, gated by the need for a valid low-privilege account, not a high-CVSS-but-low-real-risk false alarm nor a drop-everything zero-day. |
| Exploit ScenarioDerived | An attacker who holds or registers a Subscriber-level account on a WordPress site running GeoDirectory before 2.8.194 saves a front-end listing while supplying a crafted image URL that the plugin treats as a local file path. Because the path is not validated, the attacker reads a sensitive file from outside the web root (it is then re-published at a public URL) and, as a side effect, the original file is deleted - achieving both disclosure and destruction, limited to filenames carrying an allowed media extension. A public PoC reference exists via WPScan but 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
Authenticated path traversal in the GeoDirectory WordPress plugin before 2.8.194 allows any user holding a Subscriber-level account or higher to supply an image URL during front-end listing submission that the plugin then treats as a local filesystem path, reading files from outside the web root and deleting them from the server. The impact is constrained to filenames carrying an allowed media extension, but each successful hit both re-publishes the targeted file at a public URL and destroys the original as a side effect. Exploitation requires a low-privilege account (which open registration on many WordPress sites provides) and no victim interaction; EPSS is low at 0.20% (10th percentile), the issue is not in CISA KEV, and only a public PoC reference exists that is not verified as working exploit code.
RemediationAI
Vendor-released patch: update GeoDirectory to version 2.8.194 or later, which is the fixed release per the WPScan advisory (https://wpscan.com/vulnerability/ba2114a5-01e3-40e7-a7f6-673674b6501d/) and the EUVD record (https://nvd.nist.gov/vuln/detail/CVE-2026-113491); priority per vuln.today is this_month, and no vendor-documented workaround is described in the available references. Because the assessed precondition is an authenticated Subscriber-or-above account, sites that cannot update immediately can reduce exposure by closing open user registration or tightening the roles that can reach the front-end listing submission form, with the trade-off that legitimate community sign-ups or directory submissions are blocked while that restriction is in place; administrators should also review recently submitted listings for externally hosted image values pointing at local paths, since a successful exploitation leaves a publicly re-published copy of the targeted file and removes the original. After updating, audit the uploads and media directories for missing files consistent with the allowed-extension deletion side effect.
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
The flaw is a classic CWE-22 path traversal in a WordPress plugin's listing-management workflow: GeoDirectory accepts a user-controlled image URL as part of a front-end listing save and, instead of validating that the value is a remote HTTP(S) resource, resolves it as a path on the local filesystem. Because traversal sequences are not neutralised, the resolved path can escape the WordPress web root and reach arbitrary files, subject to a suffix filter that only permits names ending in an allowed media extension - which substantially narrows the target set but does not eliminate it. The operation has two distinct consequences from the same request: the file content is copied and re-published at a publicly reachable URL (confidentiality loss) and the source file is removed (integrity/availability loss on the server). The CVSS vector AV:N/AC:L/PR:L/UI:N/S:C reflects network reachability, no special attack complexity, an authenticated but low-privileged actor, no user interaction, and a scope change because the vulnerable component's behavior affects resources beyond its own security authority (files outside the web root). The CPE entry records the product as unknown:geodirectory, indicating the vendor namespace is not resolved in the CPE dictionary, so inventory matching should rely on plugin slug and version rather than CPE alone.
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:L/UI:N/S:C/C:L/I:L/A:N
Network-reachable front-end feature (AV:N/AC:L) but needs a Subscriber account (PR:L, not PR:N); reading/deleting files beyond the web app's authority gives S:C, with limited disclosure (C:L) and file deletion (I:L).
Primary rating from Vendor (WPScan).
CVSS VectorVendor: WPScan
Lifecycle Timeline
3DescriptionCVE.org
The GeoDirectory WordPress plugin before 2.8.194 does not validate a user-supplied image URL before using it as a local file path when saving a front-end listing, allowing users with Subscriber-level access and above to read files from outside the web root and to delete files on the server, limited to file names that carry an allowed media extension. A disclosed file is re-published at a public URL and its original is deleted as a side effect.
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
Path traversal exploits occur when applications use user-controlled input to construct file system paths without proper validation.
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
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
Unauthenticated visitors to WordPress sites running GeoDirectory before 2.8.194 can retrieve the title, permalink and ca
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-109221
GHSA-54m2-gc24-q2f7
NVD
CVE.org
EPSS
Vulnrichment
Exploit-DB