CVE-2026-104899 json
GeoDirectory <= 2.8.187 - Unauthenticated Local File Inclusion via 'design_type' Parameter
published 30d ago modified 27d ago also EUVD-2026-96104
- cvss
- 8.1
- version 3.1, CNA
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.6%
- EPSS 0.6% chance of exploitation in 30 days, percentile 50%
- public exploits
- 0
- none known
Summary
The GeoDirectory – WP Business Directory Plugin and Classified Listings Directory plugin for WordPress is vulnerable to Local File Inclusion in all versions up to, and including, 2.8.187 via the 'design_type' parameter parameter. This makes it possible for unauthenticated attackers to include and execute arbitrary .php files on the server, allowing the execution of any PHP code in those files. This can be used to bypass access controls, obtain sensitive data, or achieve code execution in cases where .php file types can be uploaded and included. The required nonce is trivially obtainable by any anonymous visitor, as the geodir_basic_nonce value is localized to every public frontend page via the geodir_params script object, meaning no authentication, user interaction, or specific site content is required to exploit this vulnerability.
Patch / fix
Is CVE-2026-104899 in your stack? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.
Check with FencerCISA SSVC
- Exploitation
- none
- Automatable
- no
- Technical impact
- total
- Assessed
- 29d ago
Exploit prediction
0.64% chance of exploitation in the next 30 days, higher than 50% of all scored CVEs (FIRST EPSS, 2026-11-09).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| CNA | 3.1 | 8.1 | CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H |
Affected products
- paoltaia GeoDirectory – WP Business Directory Plugin and Classified Listings Directory
Classification
- Weakness
-
- CWE-98 Improper Control of Filename for Include/Require Statement in PHP Program
- Technology feeds
References
- github.com /AyeCode/geodirectory/commit/2357d640dad7973988742a6706b3a857b6b05d52
- wordfence.com /threat-intel/vulnerabilities/id/ac817587-1403-46e2-84bf-be5fcadc5425?source=cve
- plugins.trac.wordpress.org /browser/geodirectory/tags/2.8.187/includes/widgets/class-geodir-widget-tags.php#L1064
- plugins.trac.wordpress.org /browser/geodirectory/tags/2.8.187/includes/class-geodir-ajax.php#L709
- plugins.trac.wordpress.org /browser/geodirectory/tags/2.8.187/includes/template-functions.php#L143
- plugins.trac.wordpress.org /browser/geodirectory/tags/2.8.187/includes/template-functions.php#L199
- plugins.trac.wordpress.org /changeset/3725126/geodirectory/trunk/includes/widgets/class-geodir-widget-tags.php
Sources
- CVE List CVE-2026-104899
- NVD CVE-2026-104899
Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.