CVE-2026-103913 json
GeoDirectory <= 2.8.186 - Unauthenticated SQL Injection via 'latitude' Parameter via Stored Pending Listing
published last mo. modified last mo. also EUVD-2026-91921
- cvss
- 7.5
- version 3.1, CNA
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.4%
- EPSS 0.4% chance of exploitation in 30 days, percentile 31%
- public exploits
- 0
- none known
Summary
The GeoDirectory plugin for WordPress is vulnerable to SQL Injection via the stored latitude/longitude coordinates of a listing in versions up to, and including, 2.8.186. This is due to insufficient escaping and the absence of numeric validation on coordinate values when a listing is saved, combined with the direct string interpolation of those values into a distance sub-expression in geodir_gps_query_part() that is later executed by the public wp_ajax_nopriv_geodir_widget_listings handler when a caller supplies set_post=<pending-listing-id> and sort_by=distance_asc. This makes it possible for authenticated attackers, with Subscriber-level access and above, to append additional SQL queries into already existing queries that can be used to extract sensitive information from the database.
Is CVE-2026-103913 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
- yes
- Technical impact
- partial
- Assessed
- last mo.
Exploit prediction
0.37% chance of exploitation in the next 30 days, higher than 31% of all scored CVEs (FIRST EPSS, 2026-11-09).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| CNA | 3.1 | 7.5 | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N |
Affected products
- paoltaia GeoDirectory – WP Business Directory Plugin and Classified Listings Directory
Classification
- Weakness
-
- CWE-89 Improper Neutralization of Special Elements used in an SQL Command
- Technology feeds
References
- wordfence.com /threat-intel/vulnerabilities/id/54f449f4-0a22-45c7-8a3b-9121d70b5fe4?source=cve
- plugins.trac.wordpress.org /browser/geodirectory/tags/2.8.185/includes/general-functions.php#L1312
- plugins.trac.wordpress.org /browser/geodirectory/tags/2.8.185/includes/general-functions.php#L1394
- plugins.trac.wordpress.org /browser/geodirectory/tags/2.8.185/includes/widgets/class-geodir-widget-listings.php#L862
- plugins.trac.wordpress.org /browser/geodirectory/tags/2.8.185/includes/class-geodir-ajax.php#L1464
- plugins.trac.wordpress.org /browser/geodirectory/tags/2.8.185/includes/class-geodir-post-data.php#L660
- plugins.trac.wordpress.org /changeset?reponame=&old=3723536%40geodirectory&new=3723536%40geodirectory
Sources
- CVE List CVE-2026-103913
- NVD CVE-2026-103913
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.